On 10/07/2010 04:48 AM, Patrick wrote: > > On Oct 6, 2010, at 5:20 PM, Mohamed Lrhazi wrote: > >> On Wed, Oct 6, 2010 at 7:33 PM, James Louis <jgloui...@gmail.com> wrote: >>> if an instance of puppetd is already running then you'll get that error >>> message when you try to start up another instance. also there may be a >>> puppetd.pid left from the last time it was ran. you would then have to >>> remove that pid file. >>> >> >> Thanks James. I understand. >> My question is that with --test option, the second puppetd seems to >> work fine... Is it? >> Should I just use --test option to run this second puppetd, or is >> there a better way? > > I'm guessing that it will work if you run it with the -no-deamonize option. > > You really don't want to use --test. That will have other effects.
Patrick, could you elaborate on that? Because --test is what we are using constantly here. I believe it's a tip from "Pulling strings with puppet". >From what I gathered, it's the standard way to enforce a run while puppet is also running in daemon mode, which is quite exactly what Mohammed needs. So what are the catches to be wary of? Thanks in advance, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
