Hi,
> On Thu, 2014-03-20 at 10:10:29 +0100, Ralf Jung wrote:
>> To be honest, the behaviour of OpenVZ seems to make more sense than
>> upstream Linux. I mean, what if a file called "/usr/sbin/rsyslogd
>> (deleted)" actually exists? There is no way to distinguish whether this
>> program was execute
Hi!
On Thu, 2014-03-20 at 10:10:29 +0100, Ralf Jung wrote:
> To be honest, the behaviour of OpenVZ seems to make more sense than
> upstream Linux. I mean, what if a file called "/usr/sbin/rsyslogd
> (deleted)" actually exists? There is no way to distinguish whether this
> program was executed from
Hi,
> In which case I'm inclined to say this is a bogus kernel, which
> prepends “ (deleted)” instead of appending it. You should report this
> to the server provider. And I'm in principle going to just close this
> bug report (instead of adding a workaround to s-s-d), as this might
> break other
Hi,
> This seems also suspiciously similar to Chris' kernel:
>
> ,---
> Kernel: Linux 2.6.32-042stab081.5 (SMP w/20 CPU cores)
> `---
>
> In which case I'm inclined to say this is a bogus kernel, which
> prepends “ (deleted)” instead of appending it. You should report this
> to the server provid
On Wed, 2014-03-19 at 19:42:55 +0100, Ralf Jung wrote:
> > Going over the original bug report I see this very suspicious line:
> >
> > ,---
> > chrisb@massmail:~$ sudo ls /proc/427/exe -l
> > lrwxrwxrwx 1 root root 0 Dec 6 01:33 /proc/427/exe ->
> > (deleted)/usr/sbin/rsyslogd
> > `---
> >
> >
Hi Guillem,
> If --exec is supposedly broken then this would affect any daemon using
> it, which I find a bit perplexing, and I'd have expected a ton of bug
> reports on dpkg due to broken upgrades. I've rechecked it on current
> unstable, and it still works here.
That's surprising me, too. It wor
Hi!
On Wed, 2014-03-19 at 09:26:16 +0100, Ralf Jung wrote:
> this issue is still present in current wheezy, including the backports
> package. Without taking manual steps, it results in rsyslog filling up
> the disk as log rotation is completely broken - so I'd argue it should
> have a severity of
severity 731530 important
reassign 731530 dpkg 1.16.12
thanks
Hi,
this issue is still present in current wheezy, including the backports
package. Without taking manual steps, it results in rsyslog filling up
the disk as log rotation is completely broken - so I'd argue it should
have a severity of
Am 06.12.2013 11:17, schrieb Chris Butler:
> Package: rsyslog
> Version: 5.8.11-3
> Severity: normal
>
> Dear Maintainer,
>
> Following a recent upgrade from squeeze to wheezy (although this would be
> trigged by any package update it seems), we noticed that rsyslog was not
> logging to the corre
Package: rsyslog
Version: 5.8.11-3
Severity: normal
Dear Maintainer,
Following a recent upgrade from squeeze to wheezy (although this would be
trigged by any package update it seems), we noticed that rsyslog was not
logging to the correct log file after log rotation - it was still logging to
"sys
10 matches
Mail list logo
