Adeel,
This is already how puppet operates by default if your manifest is written
correctly. You should not be explicitly telling puppet to restart your service
each time the agent runs. Instead, you should create a dependency relationship
between the service and its configuration file (and even its package). For
example, the following code ties together three resource types into one class:
class webserver {
package { 'httpd':
ensure => installed,
}
file { '/etc/httpd/conf/httpd.conf':
owner => 'root',
group => 'root',
mode => '0644',
require => Package['httpd'],
}
service { 'httpd':
ensure => running,
enable => true,
hasstatus => true,
hasrestart => true,
subscribe => File['/etc/httpd/conf/httpd.conf'],
}
}
Notice how the file resource requires the package resource, and the service
resource subscribes to the file resource. This sets up a logical dependency
chain. That the httpd service subscribes to the httpd.conf configuration file
is particularly important, because this is what tells puppet that it should
restart the httpd service any time it notices and copies over a changed
httpd.conf file. An exec resource containing a "service httpd restart" command
is not required.
--
Peter Bukowinski
On Sep 16, 2013, at 8:40 AM, Adeel Bhatti <adeelarifbha...@gmail.com> wrote:
> Thanks for your reply !
> This would be really cool if the agent can look and identify the manifect
> changes !
> I have a service restart in my class, so I want to execute that only if there
> is some change in the configuration/manifest !
> Regards
> Adeel
>
>
>
> On Monday, September 16, 2013 2:20:24 PM UTC+2, Rahul Khengare wrote:
> Hi Adeel,
> First time you have to access the puppet agent and do the certificate
> generation and signing on puppet master.
> After that you can set the runinterval parameter in pupet.conf file( puppet
> agent request the puppet master manifests at defined time interval).
> This will automatically request the manifests from puppet master continuously.
>
> puppet.conf
> ----------------
> runinterval =XX (default 30 minute)
>
> This setting can be a time interval in seconds(30 or 30s), minutes (30m),
> hours (6h), days (2d), or year (5y).
>
> For the report or status refer files present in /var/lib/puppet/state
> directory.
>
> Thanks and Regards,
> Rahul Khengare,
> NTT DATA OSS Center, Pune, India.
>
>
> On Monday, September 16, 2013 4:27:54 PM UTC+5:30, Adeel Bhatti wrote:
> Hi,
> Is it nesseccary to access the client machine and execute the agent command
> manually to take in configuration ? or if the agent can know itsself that the
> server has some changes for it !!
>
> secondly, can't we have agent's logs/status of taking in
> changes/configurations ?
> I am using open source puppet master !
>
> Adeel
>
>
> --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
