[ale] permanent process

[Charles Marcus]

> From: Danny Cox [mailto:danscox at mindspring.com]
> Sent: Thursday, April 11, 2002 7:24 AM
> To: Keith Hopkins
> Cc: David Corbin; Atlanta Linux Enthusiasts
> Subject: Re: [ale] permanent process
>
> On Thu, 2002-04-11 at 07:09, Keith Hopkins wrote:
>> David Corbin wrote:
>>> I have several processes that I would like to be up "all the time"
>>> (maintenance excluded).  Normally, this screams "inittab" at me,
>>> but given then nature of the process (networking related), I don't
>>> want them spawned right when inittab is processed.  Any suggestions
>>> on how to handle this?
>>>
>>> For the record, I'm talking about pppoe (DSL), and vtun (which runs
>>> over the pppoe).  I've had some problems lately with pppoe
>>> "disappearing".  I could easily have a script that monitors and
>>> restarts, but is this the best way?

>> A (seperate) watchdog process is good.  or, if you don't mind
>> polling no more often than every minute, cron can work too.

> 	I still like your original idea of inittab, with it's 'respawn'
> capability.  You'd have to use a wrapper script that would wait until
> the appropriate time to fire off the other processes at init time, or
> fire them off immediatly if not.  Init also has the feature of looking
> at the frequency of spawns, and if it's too fast, will disable them;
> automatically.
>
> --
> Danny

Intersting question...

I have a couple of LTSP servers (Linux Terminal Servers, www.ltso.org), and
would love the ability to ensure that there is always an OOo (OpenOffice.org
process) running, so that no user would ever experience the huge delay in
launching OOo (all of their processes run on the Server).

Is there any How-to anywhere that goes into this (the init) process in detail?

Thanks!

charles


---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.