Databases
StackOverflow2013
Postsdbo
POStartup Items - Creating a basic one
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POStartup Items - Creating a basic one
    text
    copied!<p>Please save me from a potential nervous breakdown!</p> <p>I've been following Apples documentation (see below) on how to create a Startup Item. Currently I'm just trying to get my script to print something to the console, much less actually run my app.</p> <p>Here are my two scripts, one is the startup executable, the other is the plist:</p> <pre><code>#!/bin/sh . /etc/rc.common # The start subroutine StartService() { # Insert your start command below. For example: echo "hey Eric we've started" # End example. } # The stop subroutine StopService() { # Insert your stop command(s) below. For example: echo "STOPPED ERIC" # End example. } # The restart subroutine RestartService() { # Insert your start command below. For example: echo "RESTART ERIC" # End example. } RunService "$1" { Description = "Software Update service"; Provides = ("SoftwareUpdateServer"); Requires = ("Network"); Uses = ("Network"); OrderPreference = "Late"; Messages = { start = "Starting Software Update service"; stop = "Stopping Software Update service"; }; } </code></pre> <p>Using terminal I tried to set the permissions as closely as possible as to how it is documented in the example in the link below. The odd thing was that the files didn't show the 'root' aspect to their ownership.</p> <p>I then ran SystemStarter start theApp and nothing happens. Absolutely nothing.</p> <p>Any help?</p> <p><a href="http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPSystemStartup/Articles/StartupItems.html" rel="nofollow noreferrer">http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPSystemStartup/Articles/StartupItems.html</a></p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload