OK. This may seem like a bad idea, but it's a workaround that has worked for me: I add the nfs server to the 127.0.0.1 entry of the hosts file which causes NFS to time out pretty immediately. :-\
On Wed, Nov 9, 2011 at 10:00 AM, madAndroid <andrewsta...@gmail.com> wrote: > We've only recently discovered that puppet can manage mount points > using the mount directive; > however, a short while back we built an nfs client and server classes > without using this resource, and we've encountered a problem where > puppet seems to hang when the nfs server is unavailable. > > Using --debug doesn't seem to specify exactly at which point the run > is failing, which could steer us in the right direction around putting > something in place in the classes in question. > > Is there anything we can do, short of switching over to using the > mount directive/resource, in order to mitigate the problem when the > nfs server is unavailable? It's preventing us from managing other > resources on the clients when this happens.. > > thanks in advance, > Andrew > > -- > 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. > > -- 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.
