Automate a script to start on reboot ?

[soamz]

Hi, i have a ubuntu server and I have a script in it at /usr/softwareWhenever the server reboots, I have to goto the above path and then manually start this command every time ./ooklaserver.sh start

is there a way I can automate this process, so this automatically works ?

[Lars Noodén]

If you want it to run as root, just add it to /etc/rc.local right before the line "exit 0"
If you want it to run as a particular user, then precede it with sudo

sudo -i -u soamz /usr/software/somescript

However, that way it will run when the machine itself boots, not necessarily when a user has logged in or anything like that. Nor can that method be used to launch a graphical program.

[soamz]

yes, I need it to auto run, when the machine boots due to power failure.
So, the above works ?

[Lars Noodén]

Yes, it is one method that works. Another is to use a cron job with the @reboot shortcut.

[soamz]

Okay added this,
sudo -i -u soamz /usr/software/./ooklaserver.sh start

Im on Mac terminal.
Did vi /etc/rc.local , but the esc doesnt save the file.

[ian-weisser]

Did vi /etc/rc.local , but the esc doesnt save the file.

That's right, <esc> doesn't do that in vi.
See http://www.colorado.edu/oit/services...de/vi-commands
Look under 'file management commands'

[soamz]

ALL DONE.
But the script wont start automatically.
I had to manually type it in.

I asked a friend and he said have to do cron.
So, whats the command to run the cron for this script ?

sudo -i -u soamz /usr/software/./ooklaserver.sh start

[ian-weisser]

I asked a friend and he said have to do cron.

I'm sure your friend is a nice person, but I think that's bad advice.

The reason for failure is important now.
Maybe your script relies upon environment variables that are unavailable.
Maybe your script relies upon services that aren't up yet.
Maybe your script is working just fine, but sending your output to /dev/null.
Maybe lots of possible causes.
If your job fails under rc.local, it may (or may not) fail under cron, too.

There are many ways to run a job at startup before login, or after login, or pretty much any other time you choose.
rc.local is one, and it works very well.
cron is another, and it also works very well.

[soamz]

Okay since rc.local has failed.
What shall I do now ?

[Lars Noodén]

By what symptoms does it show that it has failed to run?