[Bug 517773] Re: Drop the dd process

2010-04-02 Thread or gerson
should i try to install the rsyslog (4.2.0-2ubuntu6) package on karmic (it affects karmic too)? if its possible... -- Drop the dd process https://bugs.launchpad.net/bugs/517773 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-

[Bug 517773] Re: Drop the dd process

2010-02-17 Thread Pavel Rojtberg
I think this is not really a duplicate, but everybody with a different kernel is having fun because of this change: https://bugs.edge.launchpad.net/ubuntu/+source/rsyslog/+bug/523468 -- Drop the dd process https://bugs.launchpad.net/bugs/517773 You received this bug notification because you are a

[Bug 517773] Re: Drop the dd process

2010-02-17 Thread Martin Pitt
Right, that's the problem that was mentioned before: rsyslog needs to check if it can read from /proc/kmsg as non-root, and not drop privileges if not. In other works, seteuid(), read() -> on fail, seteuid(0) and keep it that way, on success -> setuid() -> permanently drop privs. -- Drop the dd p

[Bug 517773] Re: Drop the dd process

2010-02-17 Thread Pavel Rojtberg
after this change rsyslog started eating 100% CPU as /proc/kmsg is not user-readable here. Maybe that is because I am using the 2.6.33 kernel from the mainline-ppa, but according to this bug it should work nevertheless, right? -- Drop the dd process https://bugs.launchpad.net/bugs/517773 You rece

[Bug 517773] Re: Drop the dd process

2010-02-17 Thread Launchpad Bug Tracker
This bug was fixed in the package rsyslog - 4.2.0-2ubuntu6 --- rsyslog (4.2.0-2ubuntu6) lucid; urgency=low * debian/rsyslog.rsyslog-kmsg.upstart: - Drop this additional job; kernel changes have meant that rsyslog may read from /proc/kmsg directly after dropping privileges.

[Bug 517773] Re: Drop the dd process

2010-02-11 Thread Martin Pitt
For the record: With the current kernel it is sufficient to change $KLogPath to /proc/kmsg (in /etc/rsyslog.conf); it already does the right thing of starting as root, opening the fds, and dropping privs only afterwards (I get a fully working kern.log). So the only thing we need to add there is th

[Bug 517773] Re: Drop the dd process

2010-02-11 Thread Martin Pitt
For the impact, compare http://people.canonical.com/~pitti/bootcharts/daniel- lucid-20100212-1.png with http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100212-1 -no-rsyslog-dd.png where the desktop starts 0.7 s earlier. -- Drop the dd process https://bugs.launchpad.net/bugs/5

[Bug 517773] Re: Drop the dd process

2010-02-05 Thread Colin Watson
** Changed in: rsyslog (Ubuntu Lucid) Status: New => Triaged ** Changed in: rsyslog (Ubuntu Lucid) Milestone: None => ubuntu-10.04-beta-1 -- Drop the dd process https://bugs.launchpad.net/bugs/517773 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 517773] Re: Drop the dd process

2010-02-05 Thread Martin Pitt
The other implementation option would be to drop the dd upstart job for good, and just let rsyslogd run as root if it detects that reading from /proc/kmsg requires root. Test case schema: $ sudo python [sudo] password for martin: >>> import os >>> f=open('/proc/kmsg') >>> os.seteuid(1000) >>> f.