Thanks. Can you point me to the relevant change in the code?
Jan-Henrik Haukeland wrote: > > This has been discussed on the mailing list [1] recently and fixed in > CVS. Will be part of the next monit release. > > > [1] http://lists.gnu.org/archive/html/monit-general/2007-09/ > msg00078.html > > > On 3. okt. 2007, at 01.31, Moshe Cohen wrote: > >> Hi, >> When I try to check for a file that does not exist I get: >> /home/moshe/monitrc:30: Error: the path '/home/moshe/ff' used in >> the TIMESTAMP statement does not exist '/home/moshe/ff' >> >> This is quite disturbing as many files that I would like to test >> against do not exists when i start Monit. Actually, Monit will >> indirectly cause them to be created. >> >> I read the archives and saw this was reported a long time ago and >> the release notes for 4.8 include: >> >> * Removed a feature introduced in 4.7 which tested that a >> check-file, check-directory or check-fifo actually refered >> to an existing object of that type. Monit should not require >> these file objects to exist at startup. >> >> I am using 4.9 now and have the problem. I also tested 4.8 and >> 4.8.2 and the problem exists there too. >> >> This is an example of usage: >> check directory sbin with path /home/moshe/ff >> if changed timestamp >> then alert >> >> TIA for any help >> Moshe > > > > -- > To unsubscribe: > http://lists.nongnu.org/mailman/listinfo/monit-general > > -- View this message in context: http://www.nabble.com/cannot-check-files-or-directories-that-do-not-exists-tf4558989.html#a13014454 Sent from the monit-general mailing list archive at Nabble.com. -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general
