> > > Just for the sake of my curiosity, what was modifiying
> > > resolv.conf? Is this a security feature?
Ran into a similar "what's changing this file?" problem a while ago --
fstat(1) is your friend...
#!/bin/sh
while true
do
fstat /etc/resolv.conf >> /fstatlogfile
done
Throw that into your crontab to start at 1:58 AM (right before the
modification takes place), and be there to kill it at 2:00 (after the
modification). It's ugly, it's far from perfect, and it might not catch
really fast transitions, but it's been known to work...
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
