-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chef/Modernize/CronDFileOrTemplate matches on /etc/cron.deny #946
Comments
hey @tas50 can you please elaborate your issue. |
cron.deny and cron.allow are special files that can be placed in /etc/cron.d that allow or deny access to crontab. Their contents are completely different from regular cron.d files and as such can not be serviced by the cron_d resource. Source: https://docs.oracle.com/cd/E19253-01/817-0403/sysrescron-23/index.html I noticed that @tas50 is not even processing the file in /etc/cron.d, but in /etc instead, which should not trigger the warning at all imho. I noticed something similar with cron.daily, but will report that in a new issue. |
chef#959 fixed this, but the regression test was missing Signed-off-by: David Crosby <dcrosby@fb.com>
/etc/cron.deny is matching with the
Chef/Modernize/CronDFileOrTemplate
cop. Example:The text was updated successfully, but these errors were encountered: