On Mon, 11 May 2009, Arjen de Korte wrote: > Citeren Charles Lepple <clep...@gmail.com>: > >> I think I would really prefer that upslog didn't keep the log file > >> open, that way it doesn't matter if the log file is rotated. > > > > I'm starting to come around to this idea. For some reason, I > > thought the upslog program went into the background for a log file > > other than stdout, which would complicate error reporting, but that > > isn't the case. > > It *should* background if it isn't logging to stdout, so if it isn't, > we might have a bug here. I'm not to keen on open/close for each line > we log, for exactly the reason you mention here.
Can you elaborate? I don't see any disadvantage to doing an open/close for each line. The extra syscall load would be trivial. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
