hmm such sleeps are always really ugly... and they should IMHO not be
part of the init scripts... especially not with modern init systems like
systemd.
IMHO it should rather be sks, that e.g. either wait's for all configured
addresses to become usable, or perhaps start already with binding to the
Package: sks
Version: 1.1.1+dpkgv3-6+squeeze1
Severity: normal
When I boot my server, the screen properly shows:
"Starting sks daemons: sksdb.. sksrecon.. done."
But the sks processes are not running.
Examining the log files show that they did startup but exited prematurely.
If I now type "invok
2 matches
Mail list logo
