Another thought, since crashreporter seems to be involved (at least
from looking at this guy's explanation: http://www.dshadow.com/
software/unlockupd/) could the problem be worked around by setting
CRASHREPORTER=-NO- in /etc/hostconfig...?
That used to be something you had to do back in 10.2 to prevent
the lookupd death spirals before 10.2.8. It might work for you
here as well.
Hmm... well, I just caught it in the act with a root shell open and
I can confirm that crashdump does start when the process crashes
but just sits there indefinitely untill you kill -9 the lookupd
process, at which point it writes a crash log and mac_init re-
starts lookupd. I've now disabled crashreporterd and will see what
happens next time.
I can't glean anything useful from the logs but maybe someone else
can - I've included them below
By way of an update - disabling crashreporter does indeed seem to
work (well, it allows lookupd to die properly and get re-started) so
I'm using this as a workaround. Still no idea what was causing
lookupd to crash so much yesterday. The server was under much higher
load all day today and lookupd hsn't crashed once despite crashing 5
times yesterday. I haven't changed anything except disabling
crashreporter.
Odd.
-geoff
______________________________________
Geoff Lee <email@hidden>
Computing Support, Architecture
School of Arts, Culture and Environment
University of Edinburgh
20 Chambers St,
Edinburgh, Scotland,
EH1 1JZ
Tel: +44 (0)131 650 2341
______________________________________
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
This email sent to email@hidden
