Change Details

/etc/resolv.conf is a symlink to /private/var/run/resolv.conf on Mac OS X. Therefore stat("/etc/resolv.conf", &struct) fails, and changes to DNS are not monitored on Mac OS X. I think you need to determine if /etc/resolv.conf is a symlink and then follow it before you try to stat() it. Alternatively, you could use FSEvents on Mac to be proactively notified about changes to /etc/resolv.conf (see e.g. [1]). [1] https://github.com/emcrisostomo/fswatch/blob/master/libfswatch/src/libfswatch/c%2B%2B/fsevents_monitor.cpp

/etc/resolv.conf is a symlink to /private/var/run/resolv.conf on Mac OS X. Therefore stat("/etc/resolv.conf", &struct) monitors a file that's never modified, and changes to DNS are not discovered on Mac OS X. I think you need to determine if /etc/resolv.conf is a symlink and then follow it before you try to stat() it. Alternatively, you could use FSEvents on Mac to be proactively notified about changes to /etc/resolv.conf (see e.g. [1]). [1] https://github.com/emcrisostomo/fswatch/blob/master/libfswatch/src/libfswatch/c%2B%2B/fsevents_monitor.cpp

/etc/resolv.conf is a symlink to /private/var/run/resolv.conf on Mac OS X. Therefore stat("/etc/resolv.conf", &struct) failsmonitors a file that's never modified, and changes to DNS are not monitoreddiscovered on Mac OS X. I think you need to determine if /etc/resolv.conf is a symlink and then follow it before you try to stat() it. Alternatively, you could use FSEvents on Mac to be proactively notified about changes to /etc/resolv.conf (see e.g. [1]). [1] https://github.com/emcrisostomo/fswatch/blob/master/libfswatch/src/libfswatch/c%2B%2B/fsevents_monitor.cpp