That patch isn't right, needs to seteuid() around the read() call, but the module doesn't know what the uid is going to be; wondering whether hard-coding some number in there will upset pitti
-- rsyslogd spins CPU on some kernels https://bugs.launchpad.net/bugs/523610 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
