StartupItems - help?

[trevor_allett]

hello, thanks for reading this message.
I need to start some thing at startup (reboot) on an xserve running MacOS X 10.2.2, i have tried to set up a StartupItems by creating a dir at /Library/StartupItems/QLA_Server (this is the item, Quark license adimistrator server, this was installed and the script [QLA_Server.command] that starts it up has to be has to be double clicked from the GUI, but you can't log out without quiting it! so to the command line and add a "&" at the end) I copied another startupitem script from other sources, books and the two or three samples on the macos x hints main site BUT. . . it does not work. . . most frustrating i have tried several things eg:
/Library/StartupItems/QLA_Server
/System/Library/StartupItems/QLA_Server and others. i only restart when i have a freeze or there is an update to apply, so about once a week! if any one can help i would be grateful -t

[nosaj56]

Upload the file to my Public iDisk folder (Use iDisk Utility. user:nosaj56 pass for Public folder:appleis) and I'll try to have a working startup item by the end of the day. :D

[pink]

you may want to have a look at this:
http://www.recursive.nl/
and maybe
http://www.greasydaemon.com/macosx/macfirewall/
at least you can use them as examples.
I assume you are aware of the fact that that you cannot use anything that requires a GUI at that point in startup. So in your script you'll have to refer to a bare-bone executable ...

cheers, pink

[trevor_allett]

pink, i think this may be the problem the excutable is a ".command" file wich opens a terminal window.

[pink]

i think this may be the problem the excutable is a ".command" file wich opens a terminal window.

this should not be a problem:
if you use a startup item like a text file containing :

#!/bin/tcsh
/path/to/QLA_Server.command

there is not need for Terminal.app. (You can even rename the script to a name w/o the ".command" to make sure...)

If this doesn't work, probably the QLA Server itself needs the GUI. You may want to have a look at
/var/log/system.log
to see what is going on.

Cheers, pink