| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
| |
Created via git ls-files | xargs perl -pi -e "s/(Copyright.*?), Opscode(,)? Inc(\.)?/\\1, Chef Software Inc./gi"
|
| |
|
| |
Generated via git ls-files | xargs perl -pi -e "s/[Cc]opyright (?:\([Cc]\) )?((?\!$(date +%Y))\\d{4})(-\\d{4})?([, ][ \d]+)*(,|(?= ))/Copyright \\1-$(date +%Y),/g"
|
| |
|
|
|
|
|
| |
This is an entirely mechanically generated (chefstyle -a) change, to go
along with chef/chefstyle#5 . We should pick something and use it
consistently, and my opinion is that double quotes are the appropriate
thing.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
fix deprecation warnings
|
| |
|
|
|
|
|
| |
follows the pattern in the rspec-mocks spec tests of defining a
helper module:
https://github.com/rspec/rspec-mocks/blob/cee433c89125a3984df33c87eb61985613adce9b/spec/spec_helper.rb
|
| |
|
|
| |
conditions.
|
| |
|
|
| |
default values before
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
The opscode/chef repository now only contains the core Chef library code
used by chef-client, knife and chef-solo!
|