From the course: Red Hat Certified System Administrator (EX200) Cert Prep: 1 Deploy, Configure, and Manage (2021)

Unlock the full course today

Join today to access over 22,700 courses taught by industry experts or purchase this course individually.

Limiting access to AT and cron

Limiting access to AT and cron

From the course: Red Hat Certified System Administrator (EX200) Cert Prep: 1 Deploy, Configure, and Manage (2021)

Start my 1-month free trial

Limiting access to AT and cron

“

- [Instructor] As system administrators, we may want to limit who gets to create at or cron jobs. If so, we have four files at our disposal, at.allow and chron.allow for allowing access to the at and cron services. We have at.deny and cron.deny for denying access to at and cron services. The allow and deny files serve the exact same purposes for the respective services. When I reference the deny file, you can substitute either at.deny or cron.deny according to the service. When I reference the allow file, you can substitute either at.allow or cron.allow. The deny file's job was to deny users by name from using the service. By default, the deny file exists and is empty. The result is that nobody is denied, so everyone can create at and cron jobs. If the deny file exists, and has usernames in it, then those users are denied. The allow file's job is to allow users by name. The allow file overrides the deny file. By…

Contents