On Feb 18, 2011, at 3:01 PM, Daniel Pittman wrote: > Just to be specific: puppet doesn't do anything except use those > standard functions, so we are not actually capable of doing anything > portable to solve these problems. It really isn't so much "puppet > ignores the change to..." as "the OS libraries ignore..."
I wonder how other applications deal with it, because some of the other apps on our system noticed the change to resolv.conf in short order. Maybe they're internally stat()ing /etc/resolv.conf every so often and if the time is different, they're re-init'ing their resolver object? Seems like that's something that could happen as part of a catalog run, though, with little to no overhead.... Dunno. D -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
