rc.local runs after all the runlevel start scripts - so it's not really a good place to configure things those scripts are going to need. I've done some poking around in rc.s... [by Moray]
on 06/29/2012 – Made popular on 06/29/2012
This tutorial will show you how to automatically execute commands at the system start-up using the standard init.d directory and the default runlevel. These scripts are called init scripts or start-up scripts, they are used to start and stop services and they will be executed with root privileges.
I need to re-order init scripts, particularly so that some of my own will run before certain others. What documentation should I be looking at for thorough information on how that is done (aside from the effects of the changes).
This is in a cloud environment using the cloud-images tree, with cloud-init in the mix.
I have read the Linux FHS, but still feel a little confuse. If I have some utility shell scripts, shall I put them in /usr/bin or /usr/local/bin or ~/bin?
The FHS says the most user commands goes to /usr/bin, but it also says that administrater should install unpackaged app or host specific stuff in /usr/local, does that means the /usr/local/bin is a better place for my own scripts?
On Arch linux:
/etc/rc.local and /etc/rc.local.shutdown are good places for auto-starting scripts respectively at system startup and shutdown
Couple of questions:
Where should I add my scripts to be run at shutdown or startup
1) RHEL 6?