On 18/09/09 12:18, David Schmitt wrote: > > Ben Lavender wrote: >> Thanks for your response. >> >> I went through the type reference a little more closely. I had >> assumed that the provider => redhat (I am running rhel 5) would give >> me service xyz start/status/stop/restart on everything, but I see now >> that's not the case. Modules are being updated accordingly :) >> >> However, even after updating this and informing puppet that sshd's >> init script has a status command, sshd is not behaving correctly. >> Further investigation reveals this is actually a bug in the red hat >> init script. 'service sshd status' simply uses pidof to determine if >> sshd is running, but sshd forks off existing ssh sessions, allowing >> the daemon to be started/stopped/etc while people are still >> connected. pidof finds these and reports that sshd is running, and >> puppet has no reason not to believe the init script. > > > That's exactly the reason (I presume) why the redhat provider doesn't > set hasstatus.
I run sshd under runit and wanted to ensure that there was no sshd daemon started from the standard init script. I use this: status => "pgrep -f '/usr/sbin/sshd' -P 1" ie. check for sshd running with parent pid = 1. R. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
