guys,<br><br>you seem to be standing on your position, each one with valid points.<br>how about adding another option to close this log?<br>that way, you satisfy both needs without breaking the existing behavior by default...<br>
<br>Arno<br><br><div class="gmail_quote">2009/5/15 Daniel O'Connor <span dir="ltr"><<a href="mailto:doconnor@gsoft.com.au">doconnor@gsoft.com.au</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Fri, 15 May 2009, Arjen de Korte wrote:<br>
> Citeren Daniel O'Connor <<a href="mailto:doconnor@gsoft.com.au">doconnor@gsoft.com.au</a>>:<br>
> >> Well, one thing is that it *will* cause existing installations to<br>
> >> break, where upslog is started as 'root' and the NUT user doesn't<br>
> >> have write permissions to the log file. Obviously, send upslog a<br>
> >> SIGHUP in such case would effectively kill it (because it can't<br>
> >> reopen the log), but I know of at least one distribution (SuSE)<br>
> >> that had a default setup exactly like that. We've seen people<br>
> >> complain about this behavior before, so in all likelihood, it is<br>
> >> being used in the field.<br>
> ><br>
> > That seems broken anyway, either it expands forever and you run out<br>
> > of space or you try and rotate it and upslog stops.<br>
><br>
> If you log a few dozen bytes to the logs once every five minutes<br>
> (which boils down to about 1 kB/hr), realistically this may never<br>
> happen, so it is questionable that this is ever going to cause a<br>
> problem.<br>
<br>
</div><shrugs> depends on your /var.<br>
<br>
If it WAS a small flash embedded system 60Mb a year would not be pocket<br>
change. We still have some systems in the field with 256Mb /var's that<br>
are >50% full.<br>
<div class="im"><br>
> > IMO the SuSE package maintainer should change it to either run<br>
> > upslog as root or make a new directory iun /var/log owned but the<br>
> > NUT user..<br>
><br>
> The SuSE package maintainer did the only sensible thing here and<br>
> removed upslog from the default startup script and leave the<br>
> configuration to the user. One shouldn't run upslog without a reason.<br>
<br>
</div>I guess so, but sensible defaults are a good idea.<br>
(ie you shouldn't have to do more than enable it and pick the format to<br>
get it running).<br>
<div><div></div><div class="h5"><br>
--<br>
Daniel O'Connor software and network engineer<br>
for Genesis Software - <a href="http://www.gsoft.com.au" target="_blank">http://www.gsoft.com.au</a><br>
"The nice thing about standards is that there<br>
are so many of them to choose from."<br>
 -- Andrew Tanenbaum<br>
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C<br>
</div></div><br></blockquote></div><br>