> I don't know why you're experiencing the problem you're having, but --
> no-daemonize definitely works for me. Do you have a value for
> 'daemonize' in your config file?
No. The only way I can get it to not daemonize is to put
daemonize=false into the config file.
> You can't have the call to parse_config appear before you handle the
> cmd-line arguments because then --config won't work.
Okay, this makes sense.
> And the order of processing doesn't matter because the two types of
> values (from config file and from cli) go in different buckets, and
> access to those buckets is sorted correctly (first cli, then config,
> then defaults).
It seems that different things happen when I run it as root vs when I
run it as non-root. --genconfig only generates a configuration file
on stdout as non-root. As root, it forks and spawns a new puppetd, and
--no-daemonize is ignored. As non-root, no-daemonize and genconfig
seem to be honored.
$ puppetd --genconfig --no-daemonize | grep daemonize
daemonize = false
$ puppetd --genconfig --daemonize | grep daemonize
# daemonize = true
If I turn on debugging (-d) when running as root with --no-daemonize,
it tells me which files it is reading configs from and none of them
have content that says it should daemonize.
Is the different behavior expected when running as root vs non-root?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" 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-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
