Tested that patch, and it definitely solves the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1534106
Title:
rsyslogd crashed with SIGSEGV with juju-local configura
Fixed upstream in 8.15:
https://github.com/rsyslog/rsyslog/issues/575
Latest release 8.16 is in Debian, perhaps we could just sync up to it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.ne
You might be onto something there.. on my local juju host (where I run
the command) I had 2 DNS servers, one that knew about the .maas and one
that didn't. Changed over to the one that did and it worked.
Having said that, I didn't retry to see if it failed reliably without
said DNS.
--
You rece
Upstream Bug:
https://github.com/lxc/lxc/issues/340
Seems patches are floating around, no movement for a bit.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1339781
Title:
centos 7 nee
Thierry - thanks for the response. Is it possible to reconsider it?
Because it's not like vsftpd has its own usernames it's using the
systems user database.. so essentially vsftpd doesn't allow existing
users to login that other software does - this happens commonly in web
hosting when usernames a
Any chance of an explanation for the denial for hardy (denied by
"Thierry Carrez")
I am also a hosting company and since 6.06 we've had to patch this
ourselves.. we are now building new servers with 8.04 and find ourselves
doing it again - I'm sure we're not in that small a minority.
--
vsftpd m
