Puppet: System Administration Automated

Support

Ticket #1031 (closed defect: wontfix)

Opened 10 months ago

Last modified 10 months ago

puppetd backgrounds itself despite verbose oneshot being specified.

Reported by: digant Assigned to: community
Priority: normal Milestone:
Component: client Version: 0.24.1
Severity: minor Keywords:
Cc: Triage Stage: Unreviewed
Attached Patches: None Complexity: Unknown

Description

Running puppet in verbose, oneshot mode used to keep puppet in the foreground instead of becoming daemonized. This seems to have changed in 0.24.1 -- this is either a bug or a poor feature change.

It makes no sense to me. We run puppetd in verbose, oneshot mode specifically because we want to see the verbose information of the run and have it only run once and in the foreground (thus allowing us to see the verbose information of the run). This doesn't seem to be the case in 0.24.1

Change History

01/29/08 23:24:25 changed by pobrien

Isn't this what "--no-daemonize" is for? I understand that it is more typing and the functionality has changed but I wouldn't consider this a defect.

01/29/08 23:54:01 changed by adamhjk

  • severity changed from normal to minor.

I have to agree that I was, at the very least, caught un-aware of this change. I also watched two or three others hit it as well.

I would be okay with --verbose implying --no-daemonize.

On my installs, I just added the no-daemonize option to puppet.conf (since we use runit for managing puppetd and puppetmasterd, we don't want it to daemonize anyway.)

01/30/08 00:38:13 changed by luke

  • status changed from new to closed.
  • resolution set to wontfix.

For the record, I brought this up on the list and got no feedback saying that it mattered particularly, and it was in the changelog for 0.24.

If you're just running Puppet once in the foreground, --test is the recommended way to do that, as it includes this option and many other appropriate options.