On Tuesday, December 9, 2014 4:05:19 PM UTC-6, JonY wrote: > > Situation: client insists on ability to use a 3G modem to connect to AWS > servers (including puppet). I need a way to ensure that the 'wvdial' > process is running. It will lose the carrier and hang-up at times so I > wrote a piece of bash that (re)starts it from puppet.. but you see the > problem - if wvdial isn't running then the puppet agent will fail so the > exec script won't get run. > > Is there a way around this? Or do i need to use a cron to fix this? > > During the catalog run is too late. You need the network connection available before the catalog request is made, so that a new catalog can be retrieved -- not so much to get wvdial running but to ensure that you get an up-to-date catalog. Otherwise, you might *never* get a fresh catalog.
A task scheduler such as cron is a good way to ensure wvdial is running. As long as you're doing that, you might as well use the same scheduler, and even the same job, to run the agent. There are considerable advantages to running the agent via an external scheduler instead of as a daemon. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c23eb13a-3c56-447e-955b-1c7e7c545e6b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
