FS#3044 : some startup scripts not storing pid in files

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!

FS#3044 - some startup scripts not storing pid in files

Attached to Project: Arch Linux
Opened by Alex Matviychuk (alexmat) - Friday, 05 August 2005, 04:25 GMT
Last edited by Judd Vinet (judd) - Wednesday, 24 August 2005, 22:49 GMT

Task Type	Bug Report
Category	Packages: Current
Status	Closed
Assigned To	dorphell (dorphell)
Architecture	not specified
Severity	Low
Priority	Normal
Reported Version	0.7 Wombat
Due in Version	Undecided
Due Date	Undecided
Percent Complete
Votes	0
Private	No

Details

For example, the crond startup script executes the following code on startup:

echo $PID > /var/run/crond.pid

but if I cat /var/run/crond.pid, there's nothing there.

pidof -o %PPID /usr/sbin/crond > /var/run/crond.pid seems to work

Some daemons like ntpd don't even store a pid in a file. This affects things like process monitoring programs.

This task depends upon

Closed by dorphell (dorphell)
Saturday, 03 December 2005, 05:37 GMT
Reason for closing: Fixed