Skip to main content

List completed cron jobs in Centos


Listing cron jobs or log files within a specific time frame is quite hard especially if the log or logs are quite a big file.

But of course, doing the lazy way but a smarter way is always a good option.

Use SED or stream editor.

In Centos the log is in: /var/log/cron

/var/log - path for the file
 cron - is the file that keeps the record for cron jobs, there is no filename extension

To check the logs within the 24 hours time, sed can do it easily and quickly.

Here's one line, time saver command to check the cron log file:

sed -n '/Mar 10 00:00:01/ , /Mar 11 00:01:01/p' /var/log/cron

To redirect the output to a file:

sed -n '/Apr 10 00:00:01/ , /Apr 11 00:01:01/p' /var/log/cron > cron24_hours.record.log

You can replace /var/log/cron with any other files as long as it follows the time format of Month, Day of the month and the time in HR:MM:SS format.


Download the free Linux Android App cheat sheet, see link below. It's free. Enjoy.



Cheers..till next time!




Comments

Popular posts from this blog

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...

PowerShell Match Drive Letter to Volume ID in AWS

Matching AWS volume ID to its corresponding Windows drive letter is an easy task using PowerShell. Win32_DiskDrive holds the info for the volume-ID. Here’s the script, below enjoy 😊 $get_disks = gwmi -query "SELECT * FROM Win32_DiskDrive" ForEach ( $disk in $get_disks ){         $get_partitions = gwmi -query "ASSOCIATORS OF {Win32_DiskDrive.DeviceID=' $( $disk . DeviceID) '} WHERE AssocClass = Win32_DiskDriveToDiskPartition"     ForEach ( $partition in $get_partitions ){         $get_logicaldisks = gwmi -query "ASSOCIATORS OF {Win32_DiskPartition.DeviceID=' $( $partition . DeviceID) '} WHERE AssocClass = Win32_LogicalDiskToPartition"          ForEach ( $logicaldisk in $get_logicaldisks ){         $insert_the_dash = ( $disk . SerialNumber) . Insert( 3 , "-" ) #insert dash to match AWS v...

PowerShell get Printer Name and Driver path

Descriptive Printer name is quite useful especially if managing quite a few printers on a network. Knowing the driver path of the printers is also useful, the file can be copied and can be used to install on another computer if necessary. Here’s the PowerShell code: Get-WmiObject -Query "Select DriverPath, Name from Win32_printerdriver" -Namespace 'Root\CIMV2' | Select Name , DriverPath | ft -wrap Sample Output: Cheers..till next time. :) ================================ Free Android Apps: Click  links below to find out more: Excel Keyboard guide: https://play.google.com/store/apps/details?id=chrisjoms.myexcelapplicationguide Heaven's Dew Fall  Prayer app for Android : https://play.google.com/store/apps/details?id=soulrefresh.beautiful.prayer Catholic Rosary Guide  for Android: http...