From: Chris Ridd on
On 2008-12-15 21:26:14 +0000, Dorian Gray <D.Gray(a)picture.invalid> said:

> In article <6qnvvlFdtc5nU1(a)mid.individual.net>,
> Chris Ridd <chrisridd(a)mac.com> wrote:
>
>> You need to look at the things started by launchd, which are probably
>> set up in directories that Spotlight won't index. Grab Lingon.app,
>> which is a nice-ish GUI which shows you all that stuff.
>
> Can you give me a path to where launchd stores info about things to be
> launched, so I can fix this using Terminal?

According to launchtcl(1)

~/Library/LaunchAgents Per-user agents provided by the user.
/Library/LaunchAgents Per-user agents provided by the adminis-
trator.
/Library/LaunchDaemons System wide daemons provided by the admin-
istrator.
/System/Library/LaunchAgents Mac OS X Per-user agents.
/System/Library/LaunchDaemons Mac OS X System wide daemons.

This varies a bit on 10.4 and 10.5.

--
Chris

From: Dorian Gray on
In article <D.Gray-026029.21261415122008(a)nntp-serv.cam.ac.uk>,
Dorian Gray <D.Gray(a)picture.invalid> wrote:

> In article <6qnvvlFdtc5nU1(a)mid.individual.net>,
> Chris Ridd <chrisridd(a)mac.com> wrote:
>
> > You need to look at the things started by launchd, which are probably
> > set up in directories that Spotlight won't index. Grab Lingon.app,
> > which is a nice-ish GUI which shows you all that stuff.
>
> Can you give me a path to where launchd stores info about things to be
> launched, so I can fix this using Terminal?

P.S. ~/Library/LaunchAgents does not exist, for any of the accounts.

/Library/LaunchAgents
/Library/LaunchDaemons
/System/Library/LaunchAgents
are all empty.

/System/Library/LaunchDaemons contains:
bootps.plist
com.apple.KernelEventAgent.plist
com.apple.ODSAgent.plist
com.apple.atrun.plist
com.apple.dashboard.advisory.fetch.plist
com.apple.mDNSResponder.plist
com.apple.nibindd.plist
com.apple.periodic-daily.plist
com.apple.periodic-monthly.plist
com.apple.periodic-weekly.plist
com.apple.portmap.plist
com.apple.syslogd.plist
com.apple.usbmuxd.plist*
com.apple.xgridagentd.plist
com.apple.xgridcontrollerd.plist
com.vix.cron.plist
comsat.plist
distccd.plist
eppc.plist
exec.plist
finger.plist
ftp.plist
login.plist
nmbd.plist
ntalk.plist
org.isc.named.plist
org.postfix.master.plist
org.xinetd.xinetd.plist
printer.plist
shell.plist
smbd.plist
ssh.plist
swat.plist
telnet.plist
tftp.plist

Mac OS X.4.11.
From: Dorian Gray on
In article <6qo144Fdq7gvU1(a)mid.individual.net>,
Chris Ridd <chrisridd(a)mac.com> wrote:

> On 2008-12-15 21:26:14 +0000, Dorian Gray <D.Gray(a)picture.invalid> said:
>
> > Can you give me a path to where launchd stores info about things to be
> > launched, so I can fix this using Terminal?
>
> According to launchtcl(1)
<snip>

Ah, our posts crossed in the mail. See my other post with the contents
of the relevant directories.
From: Chris Ridd on
On 2008-12-15 21:40:22 +0000, Dorian Gray <D.Gray(a)picture.invalid> said:

> In article <D.Gray-026029.21261415122008(a)nntp-serv.cam.ac.uk>,
> Dorian Gray <D.Gray(a)picture.invalid> wrote:
>
>> In article <6qnvvlFdtc5nU1(a)mid.individual.net>,
>> Chris Ridd <chrisridd(a)mac.com> wrote:
>>
>>> You need to look at the things started by launchd, which are probably
>>> set up in directories that Spotlight won't index. Grab Lingon.app,
>>> which is a nice-ish GUI which shows you all that stuff.
>>
>> Can you give me a path to where launchd stores info about things to be
>> launched, so I can fix this using Terminal?
>
> P.S. ~/Library/LaunchAgents does not exist, for any of the accounts.

Try asking launchctl (sorry I misspelled it) directly, using the list
and bslist options. It may look in other places.

Failing that, try looking in the BOM for the package that provided the
Brother Control Center and see where it dumped stuff.

--
Chris

From: Dorian Gray on
In article <6qo1ilFdqs0lU1(a)mid.individual.net>,
Chris Ridd <chrisridd(a)mac.com> wrote:

> Try asking launchctl (sorry I misspelled it) directly, using the list
> and bslist options. It may look in other places.

launchctl list
returns nothing

launchctl: unknown subcommand "bslist"

> Failing that, try looking in the BOM for the package that provided the
> Brother Control Center and see where it dumped stuff.

lsbom
/Library/Receipts/BrotherTWAIN.pkg/Contents/Resources/BrotherTWAIN.bom

shows where everything was installed, but the relevant parts are gleaned
from the following:

$ ls /Library/Printers/Brother/Utilities
BrStatusMonitor.app/ DeviceSelector/
ControlCenter/ Server/
$ ls /Library/Printers/Brother/Utilities/ControlCenter/
ControlCenter.app/
$ ls /Library/Printers/Brother/Utilities/DeviceSelector/
DeviceSelector.app/
$ ls /Library/Printers/Brother/Utilities/Server
LOGINserver.app/ NETserver.app/ USBserver.app/

I'm still lost.

Running BrotherTWAIN.pkg itself does not allow to uninstall,[1] assuming
that's what I want to do. I would be happier just to be able to turn
off the auto-launch.

[1] It only allows an "upgrade", which I did not perform.