• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer navigation

The Geek Diary

  • OS
    • Linux
    • CentOS/RHEL
    • VCS
  • Interview Questions
  • Database
    • MariaDB
  • DevOps
    • Docker
    • Shell Scripting
  • Big Data
    • Hadoop
    • Cloudera
    • Hortonworks HDP

UNIX / Linux : How crontab validates the access based on the cron.allow and cron.deny files

by admin

To allow or deny access to specific users, crontab uses the files /etc/cron.allow and /etc/cron.deny. Based on the existence of /etc/cron.allow and /etc/cron.deny files, crontab decides whom to give access to cron in following order.

  1. If cron.allow exists – only the users listed in the file cron.allow will get an access to crontab.
  2. If cron.allow does not exist – all users except the users listed into cron.deny can use crontab
  3. If neither of the file exists – only the root can use crontab
  4. If a user is listed in both cron.allow and cron.deny – that user can use crontab.

Filed Under: Linux

Some more articles you might also be interested in …

  1. Running repairs on XFS Filesystems
  2. The /var/log/messages is empty, and so are the rotated log files such as messages.0, messages.1
  3. balena Command Examples (Interact with the balenaCloud, openBalena and the balena API from the command-line)
  4. tar Command Examples in Linux
  5. hlint: command not found
  6. DNS configuration file /etc/named.rfc1912.zones explained
  7. CentOS / RHEL 6 : How to Disable / Enable direct root login via telnet
  8. rpm: Command Examples in Linux
  9. keyctl: command not found
  10. qm clone Command Examples in Linux

You May Also Like

Primary Sidebar

Recent Posts

  • glab Command Examples
  • “glab repo” Command Examples
  • “glab release” Command Examples
  • “glab pipeline” Command Examples

© 2023 · The Geek Diary

  • Archives
  • Contact Us
  • Copyright