John, So for you an application setting of only use syslog. For me I like a text file in the directory that my project is in. One that says, hey I didn't run to completion and here is where I stopped failing that the last thing that the developers thought to write out and wasn't wiped out by a multi-tasking system was ....
I don't expect perfection just a hint of where to start to looking for imperfections I can influence. Steve Meier On Fri, 2009-01-16 at 21:37 -0700, John Doty wrote: > On Jan 16, 2009, at 9:09 PM, Steve Meier wrote: > > > To me the idea of a app.log associated with a project is that if some > > step in the project goes "GAK" I would like to know why. > > > > The basic problem is that the software's point of view is not the > user's. Software is even better than priests at "straining out gnats > and swallowing camels". syslog() is designed to archive messages for > a reasonable time, so the user can find the rare useful message if > necessary. > > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > j...@noqsi.com > > > > > _______________________________________________ > geda-user mailing list > geda-user@moria.seul.org > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user