https://bugzilla.novell.com/show_bug.cgi?id=732910 https://bugzilla.novell.com/show_bug.cgi?id=732910#c38 --- Comment #38 from Neil Rickert <nrickert@ameritech.net> 2011-12-24 17:29:40 UTC ---
There is "an" error in the execve- call, as the "execve ..." message wouldn't otherwise be reflected in the logs.
The only logs I am seeing of execve problems, are after dhclient-script has been corrupted. Here's my most recent such message: Dec 18 08:30:24 nwr2 dhclient: execve (/sbin/dhclient-script, ...): Exec format error I have rebooted and had lease renewals since then, with no such messages. But that's DEBUG turned on, which acts as a workaround to prevent corruption. Hmm, there's a thought. I expect the next lease renewal this evening. So I will deliberately sabotage dhclient-script to force that "log_error" call. If the error is logged, then stderr is still open at that point in the child process, so we are looking for a "close on exec" problem. If the error is not logged, then stderr has already been inappropriately closed. Looking at the main dhclient process with "lsof", the lease file is open with fd=4 Hmm, maybe it's just me. But that "fclose(leaseFile)" looks like poor logic to me. I think it is better to use close(fileno(leaseFile)); If there is unwritten buffered data, and you fclose() in the child process it will be written then and later written again in the parent process. Just closing the file descriptor should avoid that. Perhaps an fflush() was already done, so it won't matter. -- 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.