auto-running a script as daemon

Martin Gregorie

Tony van der Hoff wrote:
> On 5 Dec at 16:25 Gordon Henderson <gordon+usenet@drogon.net> wrote in
> message <fj6jdf$20if$1@energise.enta.net>
>
>> In article <gemini.jsl2w1005t6v4052s.news@nospam.vanderhoff.o rg>, Tony van
>> der Hoff <news_0711@vanderhoff.org> wrote:
>>> I have a perl script to monitor various bits of my server, which I run
>>> as root: /usr/local/sbin/monitor.pl &
>>>
>>> That works fine, but I'd really like to start it automatically on
>>> reboot. How would I organise that?
>> It varies from distro to distro... Eg. Debian look in /etc/init.d for a
>> file called skeleton - this is a bash script, so copy this to eg
>> /etc/init.d/monitorMyStuff and edit to start your own thing, then run
>
> Thanks, Gordon; my distro doesn't have that; I can only see things like
> "Program Files", and "My Documents and Settings".
>
> Um, not really , but I'm running Mandriva, which has its roots in red hat,
> and what Geoff described was ideal.
>
If your distro is RedHat-like, there is a bit of help:
- there's no example script, but its easy enough to find something
suitable in /etc/rc.d/init.d, copy it and edit it. At a minimum
it should have sections that implement start, stop, status and restart
requests. The vs-ftp or sshd scripts are reasonable starting points.

- use the "chkconfig" command to set up the symlinks in /etc/rc.d/rc.n
(where 'n' is the run level) that are used to start or stop the
service whenever the runlevel is changed

- use the "service" command to start, stop and restart the service or
query its status.

chkconfig and service can only be run as root.


--
martin@ | Martin Gregorie
gregorie. | Es***, UK
org |

Martin Gregorie

Tony van der Hoff wrote:
> On 5 Dec at 16:25 Gordon Henderson <gordon+usenet@drogon.net> wrote in
> message <fj6jdf$20if$1@energise.enta.net>
>
>> In article <gemini.jsl2w1005t6v4052s.news@nospam.vanderhoff.o rg>, Tony van
>> der Hoff <news_0711@vanderhoff.org> wrote:
>>> I have a perl script to monitor various bits of my server, which I run
>>> as root: /usr/local/sbin/monitor.pl &
>>>
>>> That works fine, but I'd really like to start it automatically on
>>> reboot. How would I organise that?
>> It varies from distro to distro... Eg. Debian look in /etc/init.d for a
>> file called skeleton - this is a bash script, so copy this to eg
>> /etc/init.d/monitorMyStuff and edit to start your own thing, then run
>
> Thanks, Gordon; my distro doesn't have that; I can only see things like
> "Program Files", and "My Documents and Settings".
>
> Um, not really , but I'm running Mandriva, which has its roots in red hat,
> and what Geoff described was ideal.
>
If your distro is RedHat-like, there is a bit of help:
- there's no example script, but its easy enough to find something
suitable in /etc/rc.d/init.d, copy it and edit it. At a minimum
it should have sections that implement start, stop, status and restart
requests. The vs-ftp or sshd scripts are reasonable starting points.

- use the "chkconfig" command to set up the symlinks in /etc/rc.d/rc.n
(where 'n' is the run level) that are used to start or stop the
service whenever the runlevel is changed

- use the "service" command to start, stop and restart the service or
query its status.

chkconfig and service can only be run as root.


--
martin@ | Martin Gregorie
gregorie. | Es***, UK
org |

Will Kemp

On Wed, 05 Dec 2007 15:55:13 +0000, Tony van der Hoff wrote:

> I have a perl script to monitor various bits of my server, which I run
> as root: /usr/local/sbin/monitor.pl &
>
> That works fine, but I'd really like to start it automatically on
> reboot. How would I organise that?

What other people have suggested is good, but personally i'd do it more
simply. For simple custom stuff like this, i can't be bothered with all
that runlevel / rcx.d stuff - there's no need.

I'd just add a line at the bottom of /etc/rc.d/rc.local to start it on
boot. (rc.local is run after the system startup scripts at boot time.) If
you're not concerned about it stopping tidily - i.e., you don't mind it
just being killed unceremoniously on shutdown - this is usually the
simplest way.

If you want it to do anything special on shutdown, then you'll probably
be better off doing as others have suggested.

Will

Will Kemp

On Wed, 05 Dec 2007 15:55:13 +0000, Tony van der Hoff wrote:

> I have a perl script to monitor various bits of my server, which I run
> as root: /usr/local/sbin/monitor.pl &
>
> That works fine, but I'd really like to start it automatically on
> reboot. How would I organise that?

What other people have suggested is good, but personally i'd do it more
simply. For simple custom stuff like this, i can't be bothered with all
that runlevel / rcx.d stuff - there's no need.

I'd just add a line at the bottom of /etc/rc.d/rc.local to start it on
boot. (rc.local is run after the system startup scripts at boot time.) If
you're not concerned about it stopping tidily - i.e., you don't mind it
just being killed unceremoniously on shutdown - this is usually the
simplest way.

If you want it to do anything special on shutdown, then you'll probably
be better off doing as others have suggested.

Will

Will Kemp

On Wed, 05 Dec 2007 15:55:13 +0000, Tony van der Hoff wrote:

> I have a perl script to monitor various bits of my server, which I run
> as root: /usr/local/sbin/monitor.pl &
>
> That works fine, but I'd really like to start it automatically on
> reboot. How would I organise that?

What other people have suggested is good, but personally i'd do it more
simply. For simple custom stuff like this, i can't be bothered with all
that runlevel / rcx.d stuff - there's no need.

I'd just add a line at the bottom of /etc/rc.d/rc.local to start it on
boot. (rc.local is run after the system startup scripts at boot time.) If
you're not concerned about it stopping tidily - i.e., you don't mind it
just being killed unceremoniously on shutdown - this is usually the
simplest way.

If you want it to do anything special on shutdown, then you'll probably
be better off doing as others have suggested.

Will

Will Kemp

On Wed, 05 Dec 2007 15:55:13 +0000, Tony van der Hoff wrote:

> I have a perl script to monitor various bits of my server, which I run
> as root: /usr/local/sbin/monitor.pl &
>
> That works fine, but I'd really like to start it automatically on
> reboot. How would I organise that?

What other people have suggested is good, but personally i'd do it more
simply. For simple custom stuff like this, i can't be bothered with all
that runlevel / rcx.d stuff - there's no need.

I'd just add a line at the bottom of /etc/rc.d/rc.local to start it on
boot. (rc.local is run after the system startup scripts at boot time.) If
you're not concerned about it stopping tidily - i.e., you don't mind it
just being killed unceremoniously on shutdown - this is usually the
simplest way.

If you want it to do anything special on shutdown, then you'll probably
be better off doing as others have suggested.

Will

Will Kemp

On Wed, 05 Dec 2007 15:55:13 +0000, Tony van der Hoff wrote:

> I have a perl script to monitor various bits of my server, which I run
> as root: /usr/local/sbin/monitor.pl &
>
> That works fine, but I'd really like to start it automatically on
> reboot. How would I organise that?

What other people have suggested is good, but personally i'd do it more
simply. For simple custom stuff like this, i can't be bothered with all
that runlevel / rcx.d stuff - there's no need.

I'd just add a line at the bottom of /etc/rc.d/rc.local to start it on
boot. (rc.local is run after the system startup scripts at boot time.) If
you're not concerned about it stopping tidily - i.e., you don't mind it
just being killed unceremoniously on shutdown - this is usually the
simplest way.

If you want it to do anything special on shutdown, then you'll probably
be better off doing as others have suggested.

Will

Will Kemp

On Wed, 05 Dec 2007 15:55:13 +0000, Tony van der Hoff wrote:

> I have a perl script to monitor various bits of my server, which I run
> as root: /usr/local/sbin/monitor.pl &
>
> That works fine, but I'd really like to start it automatically on
> reboot. How would I organise that?

What other people have suggested is good, but personally i'd do it more
simply. For simple custom stuff like this, i can't be bothered with all
that runlevel / rcx.d stuff - there's no need.

I'd just add a line at the bottom of /etc/rc.d/rc.local to start it on
boot. (rc.local is run after the system startup scripts at boot time.) If
you're not concerned about it stopping tidily - i.e., you don't mind it
just being killed unceremoniously on shutdown - this is usually the
simplest way.

If you want it to do anything special on shutdown, then you'll probably
be better off doing as others have suggested.

Will

Will Kemp

On Wed, 05 Dec 2007 15:55:13 +0000, Tony van der Hoff wrote:

> I have a perl script to monitor various bits of my server, which I run
> as root: /usr/local/sbin/monitor.pl &
>
> That works fine, but I'd really like to start it automatically on
> reboot. How would I organise that?

What other people have suggested is good, but personally i'd do it more
simply. For simple custom stuff like this, i can't be bothered with all
that runlevel / rcx.d stuff - there's no need.

I'd just add a line at the bottom of /etc/rc.d/rc.local to start it on
boot. (rc.local is run after the system startup scripts at boot time.) If
you're not concerned about it stopping tidily - i.e., you don't mind it
just being killed unceremoniously on shutdown - this is usually the
simplest way.

If you want it to do anything special on shutdown, then you'll probably
be better off doing as others have suggested.

Will

Will Kemp

On Wed, 05 Dec 2007 15:55:13 +0000, Tony van der Hoff wrote:

> I have a perl script to monitor various bits of my server, which I run
> as root: /usr/local/sbin/monitor.pl &
>
> That works fine, but I'd really like to start it automatically on
> reboot. How would I organise that?

What other people have suggested is good, but personally i'd do it more
simply. For simple custom stuff like this, i can't be bothered with all
that runlevel / rcx.d stuff - there's no need.

I'd just add a line at the bottom of /etc/rc.d/rc.local to start it on
boot. (rc.local is run after the system startup scripts at boot time.) If
you're not concerned about it stopping tidily - i.e., you don't mind it
just being killed unceremoniously on shutdown - this is usually the
simplest way.

If you want it to do anything special on shutdown, then you'll probably
be better off doing as others have suggested.

Will