summaryrefslogtreecommitdiff
path: root/lib/chef/daemon.rb
Commit message (Collapse)AuthorAgeFilesLines
* Retain the runlock created during daemonization for the lifetime of the process.sersut2013-10-101-1/+2
|
* Use RunLock while daemonizing which is based on flock to prevent race ↵sersut2013-10-091-68/+6
| | | | conditions.
* Normalize whitespace on all filesSeth Vargo2013-09-261-14/+14
|
* Handle pid file appropriately in forked processBrandon Adams2013-04-111-4/+24
| | | | | | | | | | | | | | | | Code and tests to keep a daemonized chef-client's forked process from reaping the parent pid file. Without this fix a forked process will reap its parent's pid file, breaking init script functionality. A start call to the init script will then launch a new process, since the init script is ignorant of the already running process. A process is considered a fork in case the chef-client daemon is running and the process pid is not equal to the pid defined in the pidfile, or if the chef-client daemon is not running and the parent pid of the process is 1, implying that the process was a fork at some point and has become orphaned.
* [OC-3564] move core Chef to the repo root \o/ \m/Seth Chisamore2012-10-301-0/+172
The opscode/chef repository now only contains the core Chef library code used by chef-client, knife and chef-solo!