Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#21586 - [lighttpd] restart never works in rc.d
Attached to Project:
Arch Linux
Opened by Dan McGee (toofishes) - Thursday, 04 November 2010, 01:35 GMT
Last edited by Pierre Schmitz (Pierre) - Tuesday, 16 November 2010, 12:46 GMT
Opened by Dan McGee (toofishes) - Thursday, 04 November 2010, 01:35 GMT
Last edited by Pierre Schmitz (Pierre) - Tuesday, 16 November 2010, 12:46 GMT
|
DetailsDescription:
`/etc/rc.d/lighttpd restart` never works due to the delay (`sleep 3`) removed in r89167. Additional info: * lighttpd/1.4.28 Steps to reproduce: 1. Try a restart; I think it may be more easily reproducible if you are using something like fcgi and spawned threads. 2. See this: $ sudo /etc/rc.d/lighttpd restart :: Checking configuration [DONE] :: Stopping lighttpd [DONE] :: Starting lighttpd [FAIL] $ sudo /etc/rc.d/lighttpd restart :: Checking configuration [DONE] :: Stopping lighttpd [FAIL] $ sudo /etc/rc.d/lighttpd start :: Checking configuration [DONE] :: Starting lighttpd [DONE] Patch attached that does something slightly better than the old code; it will sleep for one second at a time until it detects the process is done and then will start it up again. FYI: there is another rather annoying "feature" this init script exhibits that I did not fix- when you call restart but it is not already running, it fails and then doesn't start at all, which is contrary to almost all other init scripts. |
This task depends upon
lighttpd-restart.patch
I have fixed these two bugs in 1.4.28-3. Good catch; seems to be never happened to me. In most cases using reload instead of restart might be a better option btw..