Re: syslogging to a customized .log file without messing with syslog.conf
Re: syslogging to a customized .log file without messing with syslog.conf
- Subject: Re: syslogging to a customized .log file without messing with syslog.conf
- From: "Jordan K. Hubbard" <email@hidden>
- Date: Wed, 1 Feb 2006 18:45:08 -0800
On Feb 1, 2006, at 5:02 PM, Michael Bartosh wrote:
On Feb 2, 2006, at 4:45 AM, Jordan K. Hubbard wrote:
Why do you need to use the deprecated syslog(3) APIs for this?
If you use asl(3), the new logging facility, you can either
dispense with the notion of a customized log file entirely since
asl(3) allows you to tag your messages with arbitrary keys that
allow them to be easily pulled out of the central log data store
later, or if you really want logging to a separate file, you can
use asl_add_log_file() along with the standard asl logging APIs to
get what you want. See asl(3).
Does Apple have plans to evangelize ASL to Linux distros, Solaris,
BSD variants, etc?
I'm not sure what you mean by "evangelize" in this context, but the
ASL code and APIs were released as open source as of Tiger, so the
other distributions are free to either adopt or clone them as they
see fit.
- Jordan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden