launchd and syslog.conf

[Jonathan del Strother]

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@...
http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev

[Kevin Van Vechten-2]

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.

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@...
http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev

[Nigel Kersten-2]

On Wed, Aug 19, 2009 at 10:39 AM, Kevin Van Vechten<kvv@...> 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@...
> http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev
>

_______________________________________________
launchd-dev mailing list
launchd-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev

[Jonathan del Strother]

On 19 Aug 2009, at 18:39, Kevin Van Vechten <kvv@...> wrote:

> There are two pieces to the puzzle.  The first step, as you've already found, is to appropriately adjust the syslog filters

Really?  A launchd.* syslog filter works for you on Leopard?  I'll
have to try it on a different machine later, because it's doing
nothing for me here.

-Jonathan
_______________________________________________
launchd-dev mailing list
launchd-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev

[Kevin Van Vechten-2]

I was referring to the *.debug filter you mentioned later in your  
original email.  Sorry for the confusion.

Kevin

On Aug 19, 2009, at 2:50 PM, Jonathan del Strother wrote:

> On 19 Aug 2009, at 18:39, Kevin Van Vechten <kvv@...> wrote:
>
>> There are two pieces to the puzzle.  The first step, as you've  
>> already found, is to appropriately adjust the syslog filters
>
> Really?  A launchd.* syslog filter works for you on Leopard?  I'll
> have to try it on a different machine later, because it's doing
> nothing for me here.

_______________________________________________
launchd-dev mailing list
launchd-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev

[Nigel Kersten-2]

So we still don't have an Apple sanctioned way to collect launchd
debugging, and launchd debugging only into a single log file?


On Wed, Aug 19, 2009 at 2:52 PM, Kevin Van Vechten<kvv@...> wrote:

> I was referring to the *.debug filter you mentioned later in your original
> email.  Sorry for the confusion.
>
> Kevin
>
> On Aug 19, 2009, at 2:50 PM, Jonathan del Strother wrote:
>
>> On 19 Aug 2009, at 18:39, Kevin Van Vechten <kvv@...> wrote:
>>
>>> There are two pieces to the puzzle.  The first step, as you've already
>>> found, is to appropriately adjust the syslog filters
>>
>> Really?  A launchd.* syslog filter works for you on Leopard?  I'll
>> have to try it on a different machine later, because it's doing
>> nothing for me here.
>
> _______________________________________________
> launchd-dev mailing list
> launchd-dev@...
> http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev
>

_______________________________________________
launchd-dev mailing list
launchd-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev

[Damien Sorresso]

On Sep 2, 2009, at 12:33 PM, Nigel Kersten wrote:
> So we still don't have an Apple sanctioned way to collect launchd
> debugging, and launchd debugging only into a single log file?

A syslog query is not an option for you?
--  
Damien Sorresso
BSD Engineering
Apple Inc.

> On Wed, Aug 19, 2009 at 2:52 PM, Kevin Van Vechten<kvv@...>  
> wrote:
>> I was referring to the *.debug filter you mentioned later in your  
>> original
>> email.  Sorry for the confusion.
>>
>> Kevin
>>
>> On Aug 19, 2009, at 2:50 PM, Jonathan del Strother wrote:
>>
>>> On 19 Aug 2009, at 18:39, Kevin Van Vechten <kvv@...> wrote:
>>>
>>>> There are two pieces to the puzzle.  The first step, as you've  
>>>> already
>>>> found, is to appropriately adjust the syslog filters
>>>
>>> Really?  A launchd.* syslog filter works for you on Leopard?  I'll
>>> have to try it on a different machine later, because it's doing
>>> nothing for me here.
>>
>> _______________________________________________
>> launchd-dev mailing list
>> launchd-dev@...
>> http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev
>>
> _______________________________________________
> launchd-dev mailing list
> launchd-dev@...
> http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev

_______________________________________________
launchd-dev mailing list
launchd-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev

[Nigel Kersten-2]

On Wed, Sep 2, 2009 at 12:56 PM, Damien Sorresso<dsorresso@...> wrote:
> On Sep 2, 2009, at 12:33 PM, Nigel Kersten wrote:
>>
>> So we still don't have an Apple sanctioned way to collect launchd
>> debugging, and launchd debugging only into a single log file?
>
> A syslog query is not an option for you?

It's an option, yes, but we'd like to be able to export selective
logs, including launch debug logs to a log server for some clients.

> -- Damien Sorresso
> BSD Engineering
> Apple Inc.
>
>> On Wed, Aug 19, 2009 at 2:52 PM, Kevin Van Vechten<kvv@...> wrote:
>>>
>>> I was referring to the *.debug filter you mentioned later in your
>>> original
>>> email.  Sorry for the confusion.
>>>
>>> Kevin
>>>
>>> On Aug 19, 2009, at 2:50 PM, Jonathan del Strother wrote:
>>>
>>>> On 19 Aug 2009, at 18:39, Kevin Van Vechten <kvv@...> wrote:
>>>>
>>>>> There are two pieces to the puzzle.  The first step, as you've already
>>>>> found, is to appropriately adjust the syslog filters
>>>>
>>>> Really?  A launchd.* syslog filter works for you on Leopard?  I'll
>>>> have to try it on a different machine later, because it's doing
>>>> nothing for me here.
>>>
>>> _______________________________________________
>>> launchd-dev mailing list
>>> launchd-dev@...
>>> http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev
>>>
>> _______________________________________________
>> launchd-dev mailing list
>> launchd-dev@...
>> http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev
>
>
>

_______________________________________________
launchd-dev mailing list
launchd-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev