Bug #3491

--one-time seems to imply --no-daemonize, but doesn't

Added by Anonymous about 3 years ago. Updated about 3 years ago.

Status:ClosedStart date:03/31/2010
Priority:NormalDue date:
Assignee:Markus Roberts% Done:

0%

Category:executables
Target version:-
Affected Puppet version:0.25.4 Branch:
Keywords:

Description

I was encountering a problem when using —onetime seemed to hide all useful warning messages, but —debug output was not hidden.

This gives the impression that Puppet is doing work without logging it, when it is in fact logging it.

The problem seems to be that the manpage documentation implies that “—onetime” means “—nodaemonize”, but it instead should indicate the two are usually needed to be used in conjunction (as we do with the documentation for —noclient wanting —listen).

Markus suggests also that we could make “—onetime” when used with “—nodaemonize” output some simple text like “Daemonizing for a single run”, implying to the user that the should not expect to see output.

I would recommend doing both.

History

#1 Updated by James Turnbull about 3 years ago

  • Status changed from Unreviewed to Accepted
  • Assignee set to Markus Roberts

Since you’ve got an opinion Markus… :)

#2 Updated by James Turnbull about 3 years ago

Fixed man pages in commit:99818ef5a00cdce50390d229f21ebd22b81eba00 in branch 0.25.x

#3 Updated by Matt Robinson about 3 years ago

  • Status changed from Accepted to Closed

commit:b49c60bd35aa216197c330934ccb0cc69982bad9 in master

Also available in: Atom PDF