At work on our linux servers, I have a standard non root account.

Unfortunately the account does not have permissions to crontab or at.

Is there a good reason to block these commands?

I can write a script that uses sleep to do the stuff I want to schedule but I would rather do it in either cron or at.

  • Why are people marking this question as too broad? I can't imagine a more specific way of phrasing this and it's a valid question. – Bratchley Feb 3 '15 at 20:44

It slightly simplifies system administration, because users can be locked out by using /etc/nologin and kill, without having to worry about processes coming back through cron or at.

It shouldn't be a big problem if you can run your own cron daemon.

  • 1
    It would be an issue if the system is rebooted and the OP isn't notified. – Bratchley Feb 4 '15 at 2:15
  • @Bratchley system reboot was indeed my primary concern. – Osama Javed Feb 4 '15 at 9:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.