Scheduling jobs is an essential part of administering Linux servers. We took a look at how to schedule jobs on Linux machine using the cron command earlier. Here\u2019s an alternative to cron \u2013 at. The primary difference between the two is that when you schedule a task using cron it execute repeatedly without the need for rescheduling. With at, on the other hand, the scheduling of a task is only for a single execution. Both of these commands have their use, and I would suggest that you get a good understanding of them both.<\/p>\n
Let\u2019s look at how to schedule a task to execute only once using the at command. First make sure that the at daemon is running using a command like this:<\/p>\n
# ps -ef | grep atd
\nroot 8231 1 0 18:10 ? 00:00:00 \/usr\/sbin\/atd<\/p>\n
If you don\u2019t see atd running start it with this command:<\/p>\n
# \/etc\/init.d\/atd start<\/p>\n
Once the daemon has been started successfully you can schedule an at task using the two options -f, for the file to be executed, and -v, for the time at which it should be executed. So if you want to execute the shell script shellscript.sh at 6:30 PM you would run the following command:<\/p>\n
# at -f shellscript.sh -v 18:30<\/p>\n
Remember that with the at command the script shellscript.sh will execute at 6:30 PM and then the scheduling will disappear. So if this is not what you desire, you are better off using cron.<\/p>\n
The at command is pretty clever in that it can take some orders in English if you like. For example, you can schedule jobs using the following syntax as well:<\/p>\n
# at -f shellscript.sh 10pm tomorrow<\/p>\n
# at -f shellscript.sh 2:50 tuesday<\/p>\n
# at -f shellscript.sh 6:00 july 11<\/p>\n
# at -f shellscript.sh 2:00 next week<\/p>\n","protected":false},"excerpt":{"rendered":"
Scheduling jobs is an essential part of administering Linux servers. We took a look at how to schedule jobs on Linux machine using the cron command earlier. Here\u2019s an alternative to cron \u2013 at. The primary difference between the two is that when you schedule a task using cron it execute repeatedly without the need… <\/p>\n