delta/ruby-gems/chef.git/lib/chef/daemon.rb, branch https_shell

chefstyle Style/AndOr fixes

2016-03-14T17:34:33+00:00

this is part of our informal style guide, lets make it formal since
clearly its not getting followed very well.

autofixing whitespace cops

2016-02-05T23:00:00+00:00

4174 Style/SpaceInsideHashLiteralBraces
1860 Style/SpaceAroundOperators
1336 Style/SpaceInsideBlockBraces
1292 Style/AlignHash
 997 Style/SpaceAfterComma
 860 Style/SpaceAroundEqualsInParameterDefault
 310 Style/EmptyLines
 294 Style/IndentationConsistency
 267 Style/TrailingWhitespace
 238 Style/ExtraSpacing
 212 Style/SpaceBeforeBlockBraces
 166 Style/MultilineOperationIndentation
 144 Style/TrailingBlankLines
 120 Style/EmptyLineBetweenDefs
 101 Style/IndentationWidth
  82 Style/SpaceAroundBlockParameters
  40 Style/EmptyLinesAroundMethodBody
  29 Style/EmptyLinesAroundAccessModifier
   1 Style/RescueEnsureAlignment

Replace all Opscode copyrights with Chef Software.

2016-02-02T22:50:29+00:00

Created via git ls-files | xargs perl -pi -e "s/(Copyright.*?), Opscode(,)? Inc(\.)?/\\1, Chef Software Inc./gi"

Copyright year update for 2016 and massive cleanup.

2016-02-02T22:43:28+00:00

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"

Use double quotes by default

2016-01-14T14:08:03+00:00

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.

Retain the runlock created during daemonization for the lifetime of the process.

2013-10-10T22:20:48+00:00

Use RunLock while daemonizing which is based on flock to prevent race conditions.

2013-10-10T00:55:40+00:00

Normalize whitespace on all files

2013-09-26T18:13:59+00:00

Handle pid file appropriately in forked process

2013-04-11T20:48:24+00:00

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/

2012-10-30T14:39:35+00:00

The opscode/chef repository now only contains the core Chef library code
used by chef-client, knife and chef-solo!