| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
When reading a unix crontab and we receive a non-zero exit status,
log the stdout and stderr to debug.
We expect exit status 1 to happen when the user does not have a
crontab, but let's log anyways for help in troubleshooting unexpected
situations.
|
| |
|
|
| |
- update unix_spec to more modern RSpec syntax
- both #read_crontab and #write_crontab use shell_out
|
| |
|
|
|
|
|
|
|
|
|
| |
Crontab on Solaris and Illumos systems with auditing enabled
audits root attempts to read non-root user crontabs. If chef-client
runs without an auditing context (as happens by default when running
in SMF), these crontab calls will fails with exit status 1.
By switching to the non-root user first (which somehow does not
require auditing), we should be able to read user crontabs without
an auditing context.
|
| | |
|
| |
|
|
| |
fix deprecation warnings
|
| | |
|
| |
|
