site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Why do you need to use the deprecated syslog(3) APIs for this? - Jordan On Feb 1, 2006, at 2:56 AM, Stephane Sudre wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/jkh%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... 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). syslog allows someone to log to a customize .log file by using a LOCAL ID and modifying the /etc/syslog.conf file (this is how ipfw is doing it on Darwin 8). Would there be a way to achieve this (custom log file) without having to mess with the syslog.conf file? This email sent to jkh@apple.com This email sent to site_archiver@lists.apple.com