Where in the documentation does it say that the disable = yes takes
precedence?
In the quoted text:
Note that the service disable attribute and
DISABLE flag can prevent a service from being
enabled despite being listed in this attribute.
It _can_
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/982704
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apache2 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
Is it possible that this bug returned?
I updated the host to ubuntu saucy and lxc was working fine with the
virtual machine jenkins. Once I updated the guest system to saucy as
well, it seemed not to boot, but I was wrong. It never reached the
runlevel (5), which it did before.
Here is the
Hello,
is there a workaround for this issue?
I want to be able to send some VAR* variables but it seems impossible at the
moment.
I have tried many different configurations.
Is there any PAM conf change I can do to disable this behaviour and
allow me to inject variables?
Regards
Alessandro
Public bug reported:
Puppet does not work without ruby-hiera package, but it also does not
have this dependency mapped:
$ sudo apt-get install puppet-common
$ sudo puppet apply /etc/puppet/manifests/site.pp --verbose
Info: Loading facts in /etc/puppet/modules/php/lib/facter/php_config.rb
Info:
Public bug reported:
I had my dovecot successfully configured for using solr for fulltext
search with dovecot on my ubuntu 13.04. Now I have upgraded to 13.10 and
I now see this in the log crashing the imapd process(and I don't quite
understand why maxfd can less than zero. I Did try disable
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.net/bugs/1241963
Title:
package spamassassin 3.3.2-6ubuntu2 failed to install/upgrade:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1242153
Title:
package nova-common 1:2013.2~rc2-0ubuntu1 failed to install/upgrade:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1241957
Title:
package squid3 3.3.8-1ubuntu3 failed to install/upgrade: ErrorMessage:
Note that the move to upstart for php5-fpm happened with Ubuntu 13.10
Its not relevant for older releases.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1242376
Title:
reload
Public bug reported:
reload php5-fpm with upstart does not work.
php5-fpm will crash and leave non-working child processes hanging around
that will block any recovery until they are killed off manually.
This is because php5-fpm does not handle SIGHUP. It results in an
uncontrolled exit. After
Sorry. I think this bug can be closed. It works now. I think it just
needed to be reindexed
** Changed in: dovecot (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
I reported it because I believe that disable should take precedence from
my reading of the man-page. Furthermore making disable overrule enable
is the most secure thing to do if there is any ambiguity about whether a
service should be enabled or disabled in the configuration file.
If you have
Correct. This packaging bug was fixed in the debian repository just
before the 3.3.0-1 release, with commit id
11a376f8348dfa2c254b19f7b29aec13940aeb92.
The ruby-hiera dependency was moved from the puppetmaster-common
package to the puppet-common package. Previously, this was only
needed by the
Thanks for submitting this bug. Can you confirm whether the jenkins
machine was auto-started by lxc-instance? If not, can you please
run 'apport-collect 1242074' to have apport upload more information,
and tell us the path and type of container, and how you created and started
it?
status:
it was autostarted
Sent from my iPad
On 20.10.2013, at 22:12, Serge Hallyn 1242...@bugs.launchpad.net wrote:
Thanks for submitting this bug. Can you confirm whether the jenkins
machine was auto-started by lxc-instance? If not, can you please
run 'apport-collect 1242074' to have apport
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I can run puppet apply with an empty manifest and also a trivial
manifest with a single static file defined, using puppet-common
3.2.4-2ubuntu2 on Saucy and without ruby-hiera installed. What exactly
is the
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Confirmed: php5-fpm(8) documents USR2 as the reload signal, and the
upstart script defaults to HUP.
Workaround (untested): add the line reload signal USR2 to
/etc/init/php5-fpm.conf.
This also exists in Debian
Hi,
I'm not using nothing specific to Hiera, but I don't know if some 3rd
party module is (stdlib?).
There are the first 15 lines of the abstracts.pp file:
node 'debian-like-linux' {
class { 'apt':
always_apt_update= false,
disable_keys =
Drat my comment got lost.
The lxc-instance job ends up starting containers as 'anonymous'. You
can see them using
lxc-list -P /var/lib/lxc_anon
The autostart code is currently being reworked but I think this is worth
fixing in older releases. It coudl be fixed in one of two ways - or
both:
21 matches
Mail list logo
