Bug#829513: Timeout for reading PIDFile is too low for some services

Christian Hofstaedtler zeha at debian.org
Mon Jul 4 00:52:06 BST 2016


Package: systemd
Version: 230-5
Severity: minor

Hi,

espeakup needs about 0.25sec on my machine from fork to writing its
pid file. When using PIDFile= in the corresponding unit file,
systemd will complain:

Jul 03 21:39:57.509264 sxl systemd[1]: Starting Software speech output for Speakup...
Jul 03 21:39:57.523409 sxl systemd[1]: espeakup.service: PID file /run/espeakup.pid not readable (yet?) after start: No such file or directory
Jul 03 21:39:57.773883 sxl systemd[1]: Started Software speech output for Speakup.

Please address:

1) error message is not clear if the PID file read is retried

2) giving a daemon only ~0.2sec to start is a bit harsh IMO

(See #796608 for more context.)

Thanks,
-- 
 ,''`.  Christian Hofstaedtler <zeha at debian.org>
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



More information about the Pkg-systemd-maintainers mailing list