https://bugzilla.novell.com/show_bug.cgi?id=732910 https://bugzilla.novell.com/show_bug.cgi?id=732910#c26 --- Comment #26 from Neil Rickert <nrickert@ameritech.net> 2011-12-22 00:19:28 UTC --- said by Phil Bertin:
The culprit so HAS to be the /sbin/dhclient6.
We cannot rule out a kernel bug. Unless I am misreading, there is a kernel bug there somewhere. I added some debugging, as mentioned in comment 23. So when the lease renewed this afternoon, I check for the debug data. It was nowhere to be seen. As I read dhclient-script: my debugging data should be appended to the end of the log file. then some asterisks and a timestamp should be appended (around line 40 of dhclient-script). And then stderr from running the script should be appended to the log file (the "exec >>2" statement a few lines down). But when I look at the logfile, the first thing I see is that "redirected to systemctl" line. So the output from the last of those steps has truncated the log file, instead of appending to the end. I have not yet tested. I am guessing that: echo string > /dev/stderr is what is truncating the log file. I would think that is a kernel bug. "/dev/stderr" is a symlink to "/dev/fd/2, and file descriptor 2 is open for append. I admittedly am not certain of the definition of "/dev/fd/n" but it seems strange for that to be able to truncate a file when the file descriptor is open for append. If that's not a kernel bug, then the line in "/etc/rc.status" that writes to "/dev/stderr" should be using ">>" rather than ">". I'm not ruling out a bug in dhclient. There seems be room here for multiple bugs. It's possible that there's a bug in "dhclient" that has been there for a long time, but not actually triggered until that "/etc/rc.status" line wrote to stderr with the move to systemd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.