[BusyBox 0001051]: crond does not manage pid file
bugs at busybox.net
bugs at busybox.net
Thu Feb 14 11:47:31 PST 2008
The following issue has been CLOSED
======================================================================
http://busybox.net/bugs/view.php?id=1051
======================================================================
Reported By: iggarpe
Assigned To: BusyBox
======================================================================
Project: BusyBox
Issue ID: 1051
Category: Standards Compliance
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 09-25-2006 08:10 PDT
Last Modified: 02-14-2008 11:47 PST
======================================================================
Summary: crond does not manage pid file
Description:
Standard crond will create /var/run/crond.pid on startup and remove it upon
termination, as many other daemons do.
This file is very useful in general, but essential to manage processes
with utilities such as monit.
======================================================================
----------------------------------------------------------------------
vda - 02-14-08 11:47
----------------------------------------------------------------------
I'm pretty sure crond will create the pidfile:
write_pidfile("/var/run/crond.pid");
If user selects CONFIG_FEATURE_PIDFILE=y, that is...
Issue History
Date Modified Username Field Change
======================================================================
09-25-06 08:10 iggarpe New Issue
09-25-06 08:10 iggarpe Status new => assigned
09-25-06 08:10 iggarpe Assigned To => BusyBox
02-14-08 11:47 vda Status assigned => closed
02-14-08 11:47 vda Note Added: 0004774
======================================================================
More information about the busybox-cvs
mailing list