I am running a small linux server at home, and I am writing a script to log the temperature of the CPU cores every 5 seconds, but I need timestamps for it to be useful. So far I have something that saves the output of the sensors command into a file, and I have a command that prints the date and time. I just need to figure out how to combine those two.
I have written a script that notifies me when a value is not within a given range. All values “out of range” are logged in a set of per day files.
How can I get the age of a given file in, at least, days?
I just went through the list oft StackExchange sites for about 20 minutes trying to figure out where to post this. If you know any site more suitable, please move this question there. I’m posting this here because unix time got me thinking.
I am trying to obtain the full date (created or modified) of a particular file for passing to another program. I have tried variations of options with the ls command but none provide a full date for files less than 6 months old and I have limit usage of the options. When I try certain options I have seen trying to research this I get the following message:
The stat command’s manual page says:
I want to do a bash script that measures the launch time of a browser for that I am using an html which gets the time-stamp on-load in milliseconds using JavaScript.
I need to remove files older than 3 days with a cron job in 3 different directories. (these 3 directories are children of a parent directory /a/b/c/1 & /a/b/c/2 & /a/b/c/3) Can this be done with one line in the crontab?
I’ve just executed a long-running process from the bash prompt. In hindsight, I wish I’d run time on it, or noted down the time at which I kicked it off.
Why is a signed integer used to represent timestamps? There is a clearly defined start at 1970 that’s represented as 0, so why would we need numbers before that? Are negative timestamps used anywhere?