Forum OpenACS Q&A: Daemontools Supervise stopped service

1: Daemontools Supervise stopped service

Posted by Malte Sussdorff on 04/29/02 08:00 AM

Hello,

I wondered if anyone can tell me how to monitor my OpenACS
installation with daemontools without having to start the service when
the maschine reboots. I normally dont start Oracle unless I need to
develop, and having daemontools bring up the servers just consumes
memory unnecessarily.

Thanks in advance

2: Response to Daemontools Supervise stopped service (response to 1)

Posted by Hamilton Chua on 04/29/02 09:28 AM

Hi,

With regards to preventing daemontools from automatically starting a
service on boot, just type 'touch down' in the folder where you have
your run script.

E.g.

I have a service at /service/aolserver-myserver/ where I have my run
script and supervise folder and I don't want this service to start
up at boot.

cd /service/aolserver-myserver
touch down

That's it.

3: Response to Daemontools Supervise stopped service (response to 1)

Posted by Cynthia Kiser on 04/29/02 07:15 PM

If you don't always have servers running, why do you need to put them under supervise? I have a couple of developement servers that I don't think of as perminent so just started them from the command line. I see one of them has been running unsupervised since February.

4: Response to Daemontools Supervise stopped service (response to 1)

Posted by Tom Jackson on 04/29/02 09:33 PM

Of course it is nice to have a consistent method of starting and stopping services. I would argue that development servers are in more need for the daemontools package. The usefulness is in being able to start, stop and restart. There is even an option for start once. Almost every service I run uses daemontools svc. For web services I have a directory structure like the following:

in /web/control/server1/ :

drwxr-sr-x    2 server1 web  log
-rwx------    1 root    root run
-rw-r-----    1 server1 web  server1-nsd.tcl
drwx--s---    2 root    web  supervise 

in /web/control/server1/log/ :
-rw-r-----    1 server1 web  server1-error.log

With these permissions, anyone in the web group can control server1. More information in http://zmbh.com/daemontools-aolserver/

5: Response to Daemontools Supervise stopped service (response to 1)

Posted by Malte Sussdorff on 05/02/02 08:23 AM

Thanks for your answers, it really does the trick and I need to agree to Tom for his reasoning, why I want to do something like this. To add something to this, having Oracle, Postgres and AOLserver runnning at the same time consumes quite a bit of memory (around 300MB on my system). If I want to work on other stuff, it has some impact on performance, so I want to have a way to shut it down and start it up again, whenever I need to.