Quoting Darren Reed ([EMAIL PROTECTED]) on Fri, Oct 22, 1999 at 12:01:01AM
+1000:
> > Requirement: "The fields present in a syslog-sec message must be easily
> > parsed and unambiguously identified." Tagging seems like a good approach.
>
> Should the application generating the message do the tagging or should we
> only use tags for meta data added by the API/syslog daemon ?
I think the API should od it. The real content is then up to the application.
Easy migration path and not much to loose.
> For example, I like being able to do:
> syslog(argv[0], LOG_ALERT, "input string too long")
>
> without having to say what "input string too long" is. The API might make
> it look like this:
> ps=inputdaemon pid=12345 fp=in.inpd,2 msg="input string too long"
> (ps = process name, pid = process id, fp = facility,priority)
Sounds fine to me!
cheers
afx
--
SuSE Muenchen GmbH Phone: +49-89-42769-0
Stahlgruberring 28 Fax: +49-89-42017701
D-81829 Muenchen, Germany
May the Source be with you!
