On Thu, 2 Dec 2010 21:47:26 +0100, "=?UTF-8?Q?Jes=C3=BAs?= M. Navarro"
wrote:
> While I understand why that's the case (so there's no chance to hijack the
> system by a rogue puppetmaster upon puppet client installalation), I don't
> see why the option is not managed by debconf defaulting to "
Hi:
I've been surprised by the default to "no" too.
While I understand why that's the case (so there's no chance to hijack the
system by a rogue puppetmaster upon puppet client installalation), I don't
see why the option is not managed by debconf defaulting to "no" (won't start
at boot time).
tag 563559 + confirmed
severity 563559 minor
thanks
Hello, and thanks for reporting this issue.
The change to make puppetd not start at boot is by design, and is
documented in NEWS.Debian, as well as on the console when installing.
It is, perhaps, unfortunate that it also affects clients upgrad
Package: puppet
Version: 0.25.1-3
Severity: grave
puppet does not longer start after the upgrade from lenny to squeeze.
| Preparing to replace puppet 0.24.5-3 (using .../puppet_0.25.1-3_all.deb) ...
| Stopping puppet configuration management tool.
| Unpacking replacement puppet ...
| Processing t
4 matches
Mail list logo