Thanks John for your reply.Now I am able to see the Puppet agent process on the machine.
Satish. On Tuesday, July 8, 2014 6:35:37 PM UTC+5:30, jcbollinger wrote: > > > > On Tuesday, July 8, 2014 3:47:25 AM UTC-5, Satish Katuru wrote: >> >> Hi, >> >> I linked both Master and Agent machines.But I am unable to see the Agent >> process on Agent machine. >> Can we have the Agent process on the Agent machine? >> >> I used below command to get the latest code >> >> puppet agent -t --waitforcert=60 >> >> When I Execute it every time it would take the code from master and >> deploy it on Agent machines.But how the agent machine looks for the latest >> code on Master machine for every 30 minutes? >> >> Do we need to do any configuration settings? >> >> and >> >> How can i see the agent process on agent machine? >> >> > > You are running the agent with the -t (--test) option, which implies > several other options including --no-daemonize (but *not* --noop). If > you want to run the agent as a daemon then omit that option. Rather than > launching it manually, though, it would be better to launch it via its > service management script, which should have been installed as part of the > package (supposing you used a package, rather than a source install). On > many systems, the command would be "service puppet start". > > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/97a248d7-79cd-4dcf-8427-830168cad0f8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
