[khiltd]

I’ve seen the same behavior on Leopard clients with printers plugged directly into them. Power cycling the printer usually fixes it (temporarily).

[khiltd]

This is probably not the best place in the world to ask a general troubleshooting question regarding a Panther client machine, but I’d take a wild guess that your printer drivers are to blame for Word crashing. What’s the stack trace look like in the log?

[khiltd]

Some useful and otherwise unavailable information on the subject of launchd “sessions” from the list:

[quote]On Nov 29, 2007, at 5:14 PM, Kevin Van Vechten wrote:

Here’s a summary of sessions:

– LaunchDaemons are only loaded into the “System” session of the root launchd. No per-user launchd has a “System” session.
– Unless otherwise specified by the LimitLoadToSessionType key in the plist, LaunchAgents are loaded into the “Aqua” session.

– The “Aqua” session is the same session all GUI Applications are executed in.
– Logins via SSH, telnet, and others are executed in a “StandardIO” session.
– Each user is given a single “Background” session. Jobs in the “Background” session may live longer than the last logout of the user.[/quote]

[khiltd]

Might also want to run otool over the binaries and see what they each link against–could turn up some helpful clues.

There’s also the boot-dev and launchd-dev mailing lists, though I’m not sure how forthcoming one can expect any of the participating engineers to be.

[khiltd]

[QUOTE][u]Quote by: klktrk[/u]I think I’m left to a trial and error on that one.[/p][/QUOTE]

I’ve tried (I think) every permutation of the undocumented “bootstrap” subcommand and that’s definitely not a good idea. Seems to fire everything up and leave you stuck with no login window.

For diskutil and dscl I imagine you’d want to start with /System/Library/LaunchDaemons/com.apple.diskarbitrationd.pllist and /System/Library/LaunchDaemons/com.apple.DirectoryServicesLocal.pllist and see how far you get.

[khiltd]

It’s not much documentation, but it’s documentation nonetheless:

[code]Prior to Mac OS X 10.5, the rc script was used to bootstrap the OS. As of Leop-
ard, the system is self-bootstrapped via launchd(8) which uses the launchctl(1)
bootstrap subcommand to read in launchd jobs from the standard locations. For
compatibility reasons, the rc.local script still continues to work.[/code]

Inspection of the launchctl sources confirms that it’s calling most of the shots these days.

[khiltd]

If they don’t work you can always parse the IOKIt registry with something like

[code]ioreg -c IODVDServices -w 0 | grep -i DVD[/code]

[Author]

Posts