[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [SAGE] crontabs vs /etc/cron.[daily,hourly,*] vs. /etc/cron.d/
Am I the only one seeing and hearing Red Alert
sirens?
From a security standpoint, the per-use crontabs can be
controlled and managed.
Giving users sudo access to directories intended for
system-utility cronjobs is DANGEROUS!
Personally,
I prefer a per-user crontab. For one, it's the only thing a
plain user can
modify directly if he or she wants to manage jobs. In
addition, I believe
it's the only mechanism that works consistently on
all modern UNIXen.
However, the /etc/cron.*/ stuff is useful for
packaged
software.
I think the per user crontabs should be avoided. It's much less clear
and obvious than the crons in /etc. I find it's easier to version control them,
as people need to have root/sudo access to update them. I'm sure we've all had
instances where critical crontabs stop running after an account is disabled when
an employee leaves.
------------------------------------------------------------------------------
The information in this e-mail and any attachments are for the sole use of the intended recipient and may contain privileged and confidential information. If you are not the intended recipient, any use, disclosure, copying or distribution of this message or attachment is strictly prohibited. If you believe that you have received this e-mail in error, please contact the sender immediately and delete the e-mail and all of its attachments.
==============================================================================