Re: Feature request for config file checking?

[Rory Toma]

Just make sure that we document this feature as potentially insecure.

On Thu, 2003-06-05 at 14:06, Mark Ferlatte wrote:
> Jan-Henrik Haukeland said on Thu, Jun 05, 2003 at 09:59:42PM +0200:
> > No, this seems like a cool idea at least in my book and you're right
> > about monit almost having this function already, that is, some minor
> > extensions to the TIMESTAMP statement [1] should do the trick as in:
> > 
> > check apache with pidfile /var/run/apache.pid
> >   start program = /etc/init.d/apache start
> >   stop program = /etc/init.d/apache stop
> >   if timestamp "/local/apache/conf/httpd.conf" was changed then restart
> > 
> > It's probably easier to implement this if we only check the last-
> > modified-timestamp of a config file, but of course a changed timestamp
> > does not necessarily imply that the content of a file was changed and
> > to check for actual changes a checksum of the file is needed, as you
> > mentioned previously. Still, would just checking the last modified
> > timestamp be sufficient do you think?
>  
> I think that last modified would be enough for my needs... md5sum is probably
> overkill.
> 
> The extension to the timestamp statement would solve my problem perfectly.
> 
> M
> 
> ______________________________________________________________________
> 
> --
> To unsubscribe:
> http://mail.nongnu.org/mailman/listinfo/monit-general
-- 
Rory Toma               address@hidden
VP of Run Level 9       http://www.trs80.net
Digeo Digital           http://www.digeo.com

signature.asc
Description: This is a digitally signed message part