Bug 1944 – Not auto-starting at boot time on Mac OS X 10.4.x

Bug 1944 - Not auto-starting at boot time on Mac OS X 10.4.x

Summary:

Not auto-starting at boot time on Mac OS X 10.4.x

Status:	VERIFIED WORKSFORME

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Mac Preference Pane
Version:	6.2.0
Platform:	Macintosh MacOS X 10.4

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Blackketter Dean

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-08-08 11:21 UTC by Rich Siegel
Modified:	2009-09-08 09:27 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Rich Siegel 2005-08-08 11:21:53 UTC

I have the "Automatically start:" popup menu set to "When system boots"; however, the server does not 
automatically start up when the machine boots; I have to open the prefs pane and click the "Start Server" 
button. (This can be a bit of a drag when I'm not in front of the music server.)

I think the format of StartupItems may have changed in 10.4, but I'm not sure what the changes were or 
where they're documented.

Comment 1 Blackketter Dean 2005-08-08 11:24:33 UTC

Rich, can you try turning off the automatic start server, then turn it on again?   10.4 did introduce new 
startup system but remained backwards compatible AFAIK.

Comment 2 Rich Siegel 2005-08-08 11:30:33 UTC

Done. I will report on whether that worked the next time I restart the server machine. Thanks for the tip.

Comment 3 Blackketter Dean 2005-08-21 17:22:49 UTC

Rich, I can't reproduce this here on 10.4.  Are you running on osx server?  I'm going to close this as not 
reproducible.  If you can, please reopen.

Comment 4 Rich Siegel 2005-08-22 04:44:25 UTC

I tried your suggestion of turning the auto-start setting to "Never" and then back to "When system boots", 
and that seems to have solved the problem. I'm still curious as to how it got in that state in the first place, 
but since there seems to be a workable solution, I won't lose any sleep over it. :-)