Nope, the WA doesn't work. The logs does go to the new file but unfortunately they continue to be written at the same file offset so leaving a large chunk of blank entries.
I remember helping the CR owner to change logadm.conf and implement a SIGHUP handler in svc.startd and I don't know why the fix is not integrated yet (it was months ago...). I'll check with her. -- Renaud On 1/20/2009 10:23 PM, Nicolas Williams wrote: > On Tue, Jan 20, 2009 at 01:13:06PM -0800, Stephen Hahn wrote: >> Is the proposed workaround not sufficient as a fix? That is, couldn't >> the smf_logs rule be >> >> smf_logs -c -C 8 -s 1m /var/svc/log/*.log >> >> or do we have examples of bizarre program that seek on stdout/stderr? >> (Trying it on a machine now...) > > Is stdout/stderr not opened O_APPEND? If so then I would think that's > enough. If not then maybe SMF should be changed to open the log files > with O_APPEND. > > Looking at $SRC/cmd/svc/startd/log.c:setlog() it's clear that SMF does > open the log files with O_APPEND. > > So, yes, the -c option seems like it should be a fix, and a pretty > simple one > > Incidentally, where is smf_logs? > > Nico
