hi i have installed a program which i want it to start each time when the system starts i dunno how to do this can anyone help me and tell me what to edit ? here is the command i use to run the program from the terminal /usr/local/bin/noip2
thanks in advance
On Tuesday, May 31st 2005 at 14:50 +0300, quoth Ahmed Abdel-Aliem:
=>hi =>i have installed a program which i want it to start each time when the =>system starts =>i dunno how to do this =>can anyone help me and tell me what to edit ? =>here is the command i use to run the program from the terminal =>/usr/local/bin/noip2
Add it to /etc/rc.d/rc.local
Ahmed Abdel-Aliem wrote:
hi i have installed a program which i want it to start each time when the system starts i dunno how to do this can anyone help me and tell me what to edit ? here is the command i use to run the program from the terminal /usr/local/bin/noip2
Put the command you want to run in a script called:
/etc/rc.d/rc.local
The command should either run in the background or exit quickly, or you won't be able to log in. So if the command does not background itself, or exit after doing what it needs to do, put a "&" after the command to run it in the background.
Example:
# echo '/usr/local/bin/noip2 &' >> /etc/rc.d/rc.local # chmod +x /etc/rc.d/rc.local
Paul.
Ahmed Abdel-Aliem wrote:
hi i have installed a program which i want it to start each time when the system starts i dunno how to do this can anyone help me and tell me what to edit ? here is the command i use to run the program from the terminal /usr/local/bin/noip2
thanks in advance
crontab -e
add at the end
@reboot /usr/local/bin/noip2
On Tue, May 31, 2005 at 07:41:58AM -0500, Steven Stern wrote:
crontab -e add at the end @reboot /usr/local/bin/noip2
^^^^^^
Woah, cool. I never knew that -- very useful.
On Tue May 31 2005 8:44 am, Matthew Miller wrote:
On Tue, May 31, 2005 at 07:41:58AM -0500, Steven Stern wrote:
crontab -e add at the end @reboot /usr/local/bin/noip2
^^^^^^
Woah, cool. I never knew that -- very useful.
But what's the difference between doing it this way and adding the command to rc.local? Is it just a matter of different paths to the same end, or are there differences in the implementation?
On Tue, May 31, 2005 at 09:04:07AM -0400, Claude Jones wrote:
crontab -e add at the end @reboot /usr/local/bin/noip2
Woah, cool. I never knew that -- very useful.
But what's the difference between doing it this way and adding the command to rc.local? Is it just a matter of different paths to the same end, or are there differences in the implementation?
The cron thing is an easy way to do it as a normal user.
On Tue, 2005-05-31 at 09:05 -0400, Matthew Miller wrote:
On Tue, May 31, 2005 at 09:04:07AM -0400, Claude Jones wrote:
crontab -e add at the end @reboot /usr/local/bin/noip2
Woah, cool. I never knew that -- very useful.
But what's the difference between doing it this way and adding the command to rc.local? Is it just a matter of different paths to the same end, or are there differences in the implementation?
The cron thing is an easy way to do it as a normal user.
The cron thing also seems to avoid the hang during boot if the process kicked off by rc.local fails to end/daemonize
On Tuesday, May 31st 2005 at 08:44 -0400, quoth Matthew Miller:
=>On Tue, May 31, 2005 at 07:41:58AM -0500, Steven Stern wrote: =>> crontab -e =>> add at the end =>> @reboot /usr/local/bin/noip2 => ^^^^^^ => =>Woah, cool. I never knew that -- very useful.
I don't recommend it. Most things that happen at boot time are under root it. When you place things in rc.local you know the order they will run in. Crontab entires are typically intended to not know anything about order. To say that using this feature is obscure is an understatement. Typically, people not only don't know to look in a crontab to see what's going to happen at boot, they also don't have a convention for a location of the file to be fed to crontab to reset it when needed.
If you didn't write it down it never happened.
On Tue, May 31, 2005 at 09:09:05AM -0400, Steven W. Orr wrote:
=>> crontab -e =>> add at the end =>> @reboot /usr/local/bin/noip2 => ^^^^^^ =>Woah, cool. I never knew that -- very useful. I don't recommend it. Most things that happen at boot time are under root it. When you place things in rc.local you know the order they will run in. Crontab entires are typically intended to not know anything about order. To say that using this feature is obscure is an understatement. Typically, people not only don't know to look in a crontab to see what's going to happen at boot, they also don't have a convention for a location of the file to be fed to crontab to reset it when needed.
I agree, probably not the best for system tasks.
-
Ahmed Abdel-Aliem -
Claude Jones -
Jeff Vian -
Matthew Miller -
Paul Howarth -
SternData -
Steven W. Orr