RE: Prestart & Autostart

David,

Since the only way a daemon is used is when a connect request is 
received, this method is pretty much self managing.  But, if you are 
expecting a lot of "connect, do a tiny bit of work, disconnect" like 
an HTTP request, then you probably should come up with a better 
method.  In my case, it is "connect, do a lot of work, wait, do more 
work, disconnect"...more like a telnet session.

The think you do want to be carefull of is to clear your data queue of 
old Job ID's at startup.  You have already seen what happens when you 
have junk out there. <g>

Bob

-----Original Message-----
From:   David Gibbs [SMTP:David.Gibbs@IL.US.MKS.com]
Sent:   Thursday, May 13, 1999 11:04 AM
To:     'MIDRANGE-L@midrange.com'
Subject:        RE: Prestart & Autostart

> I use an AutoStart job to start the sockets monitor job
> (XFSOCKMON for
> me).  Then XFSOCKMON submits its own client servicing jobs (what you 
> call your daemon).  Each time a client connects, submit a new 
daemon.
>  Then the daemon's hang on your takedescriptor().

Well, we might have to do that... but we'd really like to be able to 
let the
system manage how many copies of the daemon are active.

david
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to 
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: 
david@midrange.com
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---