Your message dated Mon, 17 Mar 2014 16:03:09 +0100
with message-id <[email protected]>
and subject line puppet agent is now disabled at boot
has caused the Debian Bug report #723080,
regarding /etc/init.d/puppet: Please to not start puppet daemon by default
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
723080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723080
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: puppet
Version: 3.3.0-1
Severity: wishlist
File: /etc/init.d/puppet
It would be nice if the puppet daemon was not started by default upon
installation (for both systemd and LSB scripts).
For systemd, dh_systemd_enable already have a "--no-enable" option,
dh_installinit is still missing it (See: #709384).
I guess it would be better to wait until "--no-enable" is implemented in
dh_installinit before enabling it for systemd.
Cheers
Laurent Bigonville
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.10-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages puppet depends on:
ii init-system-helpers 1.8
ii puppet-common 3.3.0-1
ii ruby 1:1.9.3
ii ruby1.8 [ruby-interpreter] 1.8.7.358-8
ii ruby1.9.1 [ruby-interpreter] 1.9.3.448-1
ii ruby2.0 [ruby-interpreter] 2.0.0.299-1
puppet recommends no packages.
Versions of packages puppet suggests:
pn etckeeper <none>
pn puppet-el <none>
ii vim-puppet 3.3.0-1
-- no debconf information
--- End Message ---
--- Begin Message ---
The puppet agent is prevented from performing any changes at boot, using
puppet's own locking.
While not necessarily a perfect solution, it should be enough to prevent
puppet agent from making any modification no matter which init system is
used.
I'm closing this bug.
--
Stig Sandbeck Mathisen
--- End Message ---
