Path: csiph.com!goblin3!goblin.stu.neva.ru!panix!MIX!Blackbird
From: billy@MIX.COM
Newsgroups: comp.sys.mac.system
Subject: Re: Shutdown console messages
Date: Wed, 16 Sep 2015 01:10:08 +0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Lines: 30
Message-ID: <mtafhg$o2v$1@reader2.panix.com>
References: <NealReid-97C164.17575415092015@news.magma.ca> <d5rqdgFco0dU1@mid.individual.net> <NealReid-986994.20461015092015@news.magma.ca>
NNTP-Posting-Host: panix5.panix.com
X-Trace: reader2.panix.com 1442365808 24671 166.84.1.5 (16 Sep 2015 01:10:08 GMT)
X-Complaints-To: abuse@panix.com
NNTP-Posting-Date: Wed, 16 Sep 2015 01:10:08 +0000 (UTC)
Xref: csiph.com comp.sys.mac.system:79885

Neal Reid <NealReid@nagma.ca> writes, quoting
Jolly Roger <jollyroger@pobox.com>:

> > That's nebulous. Verbatim error messages would be much more helpful.
> If I could SEE them - I wouldn't be asking how to capture them! 

They could be written to dmesg, but then that gets blown away on
the next boot.

> > Try searching the /var/log/system.log file.
> That (and any other) is were they are NOT. That's the point of the question... 

To enable logging, you'll need to edit this file...

/System/Library/LaunchDaemons/com.apple.lockd.plist

...and add the -d option as shown here -

        <key>ProgramArguments</key>
        <array>
                <string>/usr/sbin/rpc.lockd -d 1</string>
        </array>

Debugging level one is probably adequate, but if not, try two.

Billy Y..
-- 
        sub     #'9+1   ,r0             ; convert ascii byte
	add     #9.+1   ,r0             ; to an integer
	bcc     20$                     ; not a number