> I am not willing to accept
And what are you going to do about that? Sue us? Sue Debian Inc. ?
> that there is no way to identify what is going on that is causing
> resolv.conf to change.
BTW, maybe one way to identify the culprit is:
- install resolvconf [ I know it sounds bad, but bear with me ].
- add a script in /etc/resolvconf/update.d, e.g.:
% cat >/etc/resolvconf/update.d/sm-tracker
#!/bin/sh
(date; ps -ef --forest) >>/var/log/sm-tracker.log
% chmod +x /etc/resolvconf/update.d/sm-tracker
- let your system run for a while and when resolv.conf changed,
look at /var/log/sm-tracker.log to see what process called resolvconf
to update /etc/resolv.conf
You can uninstall resolvconf once you've found the culprit. Of course,
this will only work if the culprit has been updated to make use of
resolvconf when installed, but that should hopefully be the case.
Stefan
