Your message dated Wed, 20 Jul 2016 01:11:45 +0200
with message-id <[email protected]>
and subject line Re: Timeout for reading PIDFile is too low for some services
has caused the Debian Bug report #829513,
regarding Timeout for reading PIDFile is too low for some services
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
829513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829513
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 <[email protected]>
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
--- End Message ---
--- Begin Message ---
Hi Christian
On Mon, 4 Jul 2016 01:52:06 +0200 Christian Hofstaedtler
<[email protected]> wrote:
> 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
I don't think this is a bug in systemd. See my followup at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796608#105
There isn't really a timeout for reading a PIDFile.
The problem is, that the espeakup parent process exits before the
child/daemon process is actually ready and has written the PIDFile.
Writing the pid file is not the correct way to signal when a daemon is
ready. So this is really a bug which needs to be fixed in espeak.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
