Re: [Puppet Users] Puppet Restarting Puppet, Puppet-Agent's resolver (was Inter-Module Dependency)

2011-02-18 Thread Derek J. Balling
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 l

Re: [Puppet Users] Puppet Restarting Puppet, Puppet-Agent's resolver (was Inter-Module Dependency)

2011-02-18 Thread Daniel Pittman
On Fri, Feb 18, 2011 at 09:09, Thomas Bellman wrote: > On 2011-02-18 17:16, Derek J. Balling wrote: > >> But also my complaint is: Why *isn't* puppet-agent noticing >> that resolv.conf has changed? This seems like something that >> would only be caused by not using the standard gethostbyname() >>

Re: [Puppet Users] Puppet Restarting Puppet, Puppet-Agent's resolver (was Inter-Module Dependency)

2011-02-18 Thread Thomas Bellman
On 2011-02-18 17:16, Derek J. Balling wrote: > But also my complaint is: Why *isn't* puppet-agent noticing > that resolv.conf has changed? This seems like something that > would only be caused by not using the standard gethostbyname() > calls and such, > since *those* should reflect the change in

Re: [Puppet Users] Puppet Restarting Puppet, Puppet-Agent's resolver (was Inter-Module Dependency)

2011-02-18 Thread Derek J. Balling
On Feb 18, 2011, at 9:29 AM, Felix Frank wrote: > Ugly workaround: Schedule the restart using atd from within the catalog > run. (I've used "at now+2min" and it works so far). Well, that's "less ugly" I suppose than the client just vanishing in the middle of a catalog-run. :-) But also my compl