Issue #7123 has been updated by Daniel Pittman.

Luke Kanies wrote:

> Nothing directly uses it - its meant to be a means of determining client 
> status, with the idea that over time we can add stats and such to it.
> I believe there are Nagios checks that use it, but I don't expect people use 
> a lot of it.

OK.  Thanks for clarifying that: I am pleased to learn it can be accessed over 
the network, and isn't just dead code.

> Do you think the processes should have any sort of ability to provide status?

In some form?  It could be useful, if it provided an actual view into the 
activities of the process, or provided some information that wasn't just a 
dummy return value to prove that you connected to the service.  It might be a 
good way to export the "process status signalling" that Bryce proposed ages 
ago, since now you could query that per-process state out of your back-end 
services and figure out what they were doing.

It might also be useful if it was something akin to the Apache status module, 
giving an overview of more than one process via the network.

Meanwhile, I filed #7315 to reflect the bit-rot in JSON rendering of the class 
that caused me to start searching for users, and led to this ticket.
----------------------------------------
Bug #7123: 'puppet status' is non-functional
https://projects.puppetlabs.com/issues/7123

Author: Luke Kanies
Status: Accepted
Priority: Normal
Assignee: Daniel Pittman
Category: Faces
Target version: 
Affected Puppet version: 2.7.0rc1
Keywords: 
Branch: 


As far as I can tell it's impossible to get anything but an exception from it.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to