![]() ![]() ![]() Every user manages their own scheduled jobs and cron configuration file. There's a cron file for each user in the /etc/cron.d/ directory, and the /etc/crontab file is system-wide. First, cron also uses a daemon ( crond) that reads different configuration files. I'll cover a few basics before playing around with cron. ![]() In this article, I'll try to be as succinct, straightforward, and practical as possible, meaning I won't be able to explore all available options for cron. My colleague Ken previously wrote a great article about cron, so I recommend you check it out, as well as my previous article about the at command, another way to schedule tasks in Linux. You can schedule tasks in numerous ways, and in this article, I will focus on the cron utility. You can apply this skill in many scenarios, such as scheduling backups, collecting system logs periodically, or automating basic and repetitive tasks. A skilled sysadmin knows when and how to programmatically schedule tasks to be executed at specific intervals, whether they're recurring or happen a set number of times. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |