Skip to main content

Scheduling the future linux tasks through Crontab

 



Scheduling the future linux tasks through Crontab:



export EDITOR=vi to specify a editor to open crontab file.


crontab -e: Edit crontab file, or create one if it doesn't already exist.


crontab -l : crontab list of cronjobs, display crontab file contents.


crontab -r :Remove your crontab file.


crontab -v :Display the last time you edited your crontab file. (This option is only available on a few systems.)


.................................................... 


Syntax of the Cron jobs:


* * * * *script/command


first *: minute (0-59)


second*: hour (0-23)


third *:day of the month (1-31)


fourth *: Month of the year (1-12)


fifth* : day of the week (0-6): 0 represents sunday.




.........,.............................. 


A line in crontab file like below removes the tmp files from /home/someuser/tmp each day at 6:30 PM.

30 18 * * * rm /home/someuser/tmp/*


Cronjob runnig everyhour:

00 * * * *  rm/home/someuser/tmp/



cron every hour to run at 15 minute of an hour..

15 * * * * rm /home/someuser/tmp/*



cron every minute:

* * * * * rm /home/someuser/tmp/*



If you want to run a script every minute at specific hour, change the value of hour field to specific value such as 11th hour.

* 11 * * *  rm /home/someuser/tmp/*



To collect the cron execution log in a file:

30 18 * * * rm /home/someuser/tmp/* >

/home/someuser/cronlogs/clean_tmp_dir.log


Crontab file location for redhat.centos.fedora: /var/spool/cron/

Comments

Post a Comment

Popular posts from this blog

patching tasks

 Patching a Linux system is a critical task to ensure that the system remains secure, stable, and up-to-date with the latest features and fixes. Here’s a comprehensive guide to the tasks involved in Linux patching: 1. Pre-Patching Preparation Backup System : Ensure you have a full system backup, including critical data, configuration files, and applications. Test the backup to verify its integrity. Check Disk Space : Verify that you have enough disk space, particularly on /var , /tmp , and /boot partitions. Review Current Patch Level : Determine the current patch level and installed packages using package management tools like yum , apt , dpkg , or rpm . Check System Logs : Review system logs to identify any issues that might affect the patching process. Test in a Staging Environment : If possible, apply patches in a staging environment that mirrors production to identify potential issues. Notify Stakeholders : Inform stakeholders about the scheduled maintenance window and expecte...
Post a Comment
Read more

Linux Prepatching tasks

 Pre-patching tasks in a Linux environment are critical to ensuring a smooth and successful patching process. These tasks help in minimizing downtime, preventing issues during the patching, and ensuring the system's stability. Here’s a checklist of common pre-patching tasks you should perform: 1. Backup Critical Data Full System Backup : Perform a full system backup, including configuration files, databases, and critical application data. Verify Backup Integrity : Ensure that the backup is complete and can be restored if necessary. 2. Review Patch Notes Understand the Patch : Review the release notes and documentation for the patches you plan to apply. Understand what is being updated and any potential impact on your system. Check Dependencies : Verify that all dependencies for the patches are met, including hardware, software, and configuration requirements. 3. Check System Health Disk Space : Ensure there is sufficient disk space available, especially on /var , /tmp , and /boot ...
Post a Comment
Read more