Questions[mtime](server)

I've setup a little cron to compress log files of my application. Generally I need todays logs, so I can compress everything that is one day old or older.

Why do the two following commands behave different?

mtime is not finding anything at all, while using msec yields the desired result?

find /var/log/myapp/cronjobs/ -type f -mtime +1 -exec gzip {} \;

find /var/log/myapp/cronjobs/ -type f -msec +86400 -exec gzip {} \;

the mtime option does not yet compress files, which are now exactly 48 hours old...

any suggestions?

Edit: Ah, no, just noted: Oldest File is 1 day, 23.xx hours - so I assume that does not yet count as "older than 1 day", cause its rounded down to 1 day - and then not considered OLDER THAN, cause its "equal to".

I created a file called as test.war. If I change it to test.war.backup by copying and renaming via cp command, is this change in mtime or ctime? What about for rename mv command, is it ctime or mtime

Is it always true that when a new file is created in a directory - the directory's mtime changes?

I'm trying to setup the watchdog daemon to run on my Fedora 12 system.

I know exactly what I want it to do ... but I'm unsure as to exactly configure it. Mainly due to inexact documentation.

What I want to do is have my system reboot if a specific file doesn't change within a certain amount of time.

To do this I'll use the file = <filename> and change = <mtime> configuration options.

The problem is, I can't figure out what value I should use for mtime.

I want the system to restart if the specified file (a web server log file) hasn't changed in 10 minutes. What value would I use for mtime?

Thanks!

I have some files on a server with the date several months ago, but they are invisible to find -mtime 7 search.

When I list them with ls -l, they look perfectly normal:

-rw-r--r-- 1 root root    347253 Jun 12 16:26 pedia_main.2010-06-12-04-25-02.sql.gz
-rw-r--r-- 1 root root 490144578 Nov 24 16:26 gsmforum_main.2010-11-24-04-25-02.sql.gz

The top file is invisible to "find . -mtime 1", but the bottom one is visible.

I almost banged my head against the wall trying to understand why. I tried some random things and came across ls --full-time command. And it shows that these two are somehow a little bit different

-rw-r--r-- 1 root root    347253 2010-06-12 16:26:20.000000000 +0400 pedia_main.2010-06-12-04-25-02.sql.gz
-rw-r--r-- 1 root root 490144578 2010-11-24 16:26:12.000000000 +0300 gsmforum_main.2010-11-24-04-25-02.sql.gz

The date seems to be ok. Bit one has +0400 as a timezone, and another one is +0300. How come find fails to find the ones with +0400?

The OS is CentOS 5.5 Final with latest updates, and ls version is (GNU coreutils) 5.97.

Also, the thing is that I don't understand where this "timezone" of the file is stored. The inode does not have any extra attributes to store them it seems. The file system on the server is ext4.