What initiates an INETD job?

I recently created a socket instance program that runs under INETD. I have
a 30 second delay (on the recv) for the socket instance so that if no data
is received after 30 seconds the program ends. This morning I noticed that
there are hundreds of job logs for this job in QEZJOBLOG dating back to
12/15.

But since this program isn't in production and I am the only one testing
it at the moment, and I didn't reference the program at all yesterday
(actually since Friday the 18th), why do I have joblogs for jobs that are
spawning and ending approximately every two minutes? The INETD server is
active and the listener has been idle for over 94 hours.

I can see via wrkactjob the instance job appearing and then ending (hence
the joblogs). Is this normal/acceptable?

It is my (limited) understanding that the listener would/should trigger
the instance only when data was received on the INETD configured IP
address/port (and in this case there hasn't been any 'recent' activity).

Regards, Jerry

Gerald Kern - MIS Project Leader
Lotus Notes/Domino Administrator
IBM Certified RPG IV Developer
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx


This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged
information. Any unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please inform the
sender by reply e-mail and destroy this and all copies of this message.