Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.development.apps > #382
| From | Bill M <wpmccormick@just_about_everywhere.com> |
|---|---|
| Newsgroups | comp.os.linux.development.apps |
| Subject | Re: logging |
| Date | 2012-01-09 17:58 -0600 |
| Organization | A noiseless patient Spider |
| Message-ID | <jefuvb$k24$1@dont-email.me> (permalink) |
| References | <je541k$f4o$1@dont-email.me> <87r4zdn3id.fsf@sapphire.mobileactivedefense.com> <je5fvk$q33$1@dont-email.me> |
Bill M wrote, On 1/5/2012 6:41 PM: > Rainer Weikusat wrote, On 1/5/2012 5:17 PM: >> Bill M<wpmccormick@just_about_everywhere.com> writes: >>> I'm researching logging for C applications to run on Debian >>> Squeeze. Having previous experience with log4net, ported from log4j, I >>> see it has also been ported to log4c. It appears to be a project >>> without much recent activity and support. >>> >>> Does anyone here have any experience with log4c? Comments? >>> >>> Would anyone care to recommend a logger API? >> >> I'd vote for syslog as well. That's a standardized facility for >> collecting unspecified 'diagnostic output'[*] from any number of >> applications in a central place and it saves people using your >> software (even it that's only you) to deal with another logfile >> sitting in some random place (and presumably, growing and growing and >> ... until the disk is full) >> >> [*] No, that's not supposed to be an auditing log for 'events >> which occured on the system' although it is also used as such. > > > Thanks. Syslog it is then. Actually I have Rsyslogd, which appears to be > much more capable than the old syslog I was sort of familiar with. > > It looks like I should be able to setup a .conf file under > /etc/rsyslog.d and log different program's output to different log files > using a property-based filter, perhaps in combination with a traditional > facility/priority selector. Is that the right way to approach this? What > sort of additional features might I want to consider? > > Of course, I'll use the standard logrotate facility to make sure log > files don't grow forever. So I'm up and running with rsyslog. Thanks for the help. Is there some easy way (MACRO or other such device) to capture file name/line number?
Back to comp.os.linux.development.apps | Previous | Next — Previous in thread | Next in thread | Find similar
logging Bill M <wpmccormick@just_about_everywhere.com> - 2012-01-05 15:17 -0600
Re: logging Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2012-01-05 15:41 -0700
Re: logging Lew Pitcher <lpitcher@teksavvy.com> - 2012-01-05 17:56 -0500
Re: logging Bill M <wpmccormick@just_about_everywhere.com> - 2012-01-05 17:33 -0600
Re: logging Lew Pitcher <lpitcher@teksavvy.com> - 2012-01-05 19:31 -0500
Re: logging Rainer Weikusat <rweikusat@mssgmbh.com> - 2012-01-05 23:17 +0000
Re: logging Bill M <wpmccormick@just_about_everywhere.com> - 2012-01-05 18:41 -0600
Re: logging Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2012-01-05 21:16 -0700
Re: logging Bill M <wpmccormick@just_about_everywhere.com> - 2012-01-06 14:52 -0600
Re: logging Bill M <wpmccormick@just_about_everywhere.com> - 2012-01-06 16:39 -0600
Re: logging Bill M <wpmccormick@just_about_everywhere.com> - 2012-01-09 17:58 -0600
Re: logging Kaz Kylheku <kaz@kylheku.com> - 2012-01-10 00:13 +0000
csiph-web