Arnau Bria wrote:

> # /etc/init.d/pakiti status
> nightly pakiti update is enabled
> # /etc/init.d/pakiti stop
> Disabling pakiti:                                          [  OK  ]
> # /etc/init.d/pakiti status
> nightly pakiti update is disabled

Now try this:

     # /etc/init.d/pakiti start
     # /etc/init.d/pakiti status; echo $?
     # /etc/init.d/pakiti stop
     # /etc/init.d/pakiti status; echo $?

The status command should return 0 when the service is "running",
but 3 when it is not.  Init scripts not doing so is a fairly common
problem.  The vast majority of the packages in RHEL and CentOS do
the right thing, and if you find one that doesn't, you can file a
bug report with RedHat about it.  Init scripts from other sources
are not always so well behaved though...


        /Bellman

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to