[launchd-dev] launchd and syslog.conf

[Nigel Kersten]

On Wed, Aug 19, 2009 at 10:39 AM, Kevin Van Vechten<kvv at apple.com> wrote:
> There are two pieces to the puzzle.  The first step, as you've already
> found, is to appropriately adjust the syslog filters (remember to `killall
> -HUP syslogd` to reload the config files).  The second step is to instruct
> launchd to emit more log messages:
>
> $ sudo launchctl log level debug
> assuming you want to adjust the log level of the system wide launchd, or
> $ launchctl log level debug
> to get information out of the per-user launchd.
>
> If you want the information from early boot, you can put the `log level
> debug` command into /etc/launchctl.conf.

Doesn't this end up redirecting all debug messages, not just launchd ones?

I ran into this issue a while ago and failed to find a solution that
would just give me launchd debug messages to a slog file.



>
> Kevin
>
> Kevin
>
> On Aug 19, 2009, at 3:55 AM, Jonathan del Strother wrote:
>
>> Heya,
>> I had a bit of a nightmare this morning trying to get logging
>> information out of launchd.  Apple's advice is to add 'launchd.*
>> /var/log/launchd.log' to the /etc/syslog.conf file.  As far as I can
>> tell, this doesn't have any effect, and 'launchd' isn't listed as one
>> of the facilities (auth, authpriv, cron...) mentioned in the
>> syslog.conf manpage.
>>
>> I finally got some output by adding '*.debug /var/log/debug.log' to
>> syslog.conf, but it would be great if I could narrow that down some
>> more.  Any hints?
>>
>> Jonathan del Strother
>
> _______________________________________________
> launchd-dev mailing list
> launchd-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev
>