HP3000-L Archives

October 1998, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Bixby <[log in to unmask]>
Reply To:
Date:
Wed, 28 Oct 1998 09:59:19 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (46 lines)
Michael Hurdle writes:
>
> Can anybody out there address this question? It was asked specifically under
> the premise that FTPSRVR will execute under the inetd daemon under MPE/iX
> 6.0.

I'm not on 6.0 yet, but I have tested the new inetd FTPSRVR on 5.5.

> "What I was wondering was how to monitor processes that are running under
> JINETD. How do I know if the FTP monitor process or the TELNET process is
> running? There are other processes that we could be running under JINETD.
> How do you start/stop a process under JINETD? Do you need to stop the JINETD
> job and all processes it may be running in order to stop one process?"

Telnet processes run externally, outside of the JINETD process tree, under
their own JSMAIN just like any other MPE terminal session.

Everything else seems to run as a child of INETD.  So :SHOWPROC JOB=#Jnnn;TREE
will display all active INETD children.

INETD does a Berkeley listen() on sockets created for each entry in
/etc/inetd.conf.  When a new network connection is established on one of these
sockets, the appropriate child process is spawned, and the socket connection
is passed via stdin fd 0 (it should also be passed on stdout fd 1, but MPE
INETD doesn't).  INETD then goes back to listen() to the original socket for
any additional connections.  The child will run until the child decides to
terminate, either at the end of normal processing, or perhaps when the remote
client terminates the network connection.

You can edit /etc/inetd.conf and then do "INETD -c" to cause INETD to reread
inetd.conf and change which sockets it's listen()-ing on.  That shouldn't
affect any existing children that are still running.

Doing :ABORTJOB on JINETD will terminate INETD and all of its children.  MPE
still doesn't support aborting individual processes, but if the INETD child is
a POSIX program, you might be able to use the POSIX "kill" command to send a
terminate signal.  This will only work if the child is designed to listen for
such a signal, and POSIX "kill" *must* be executed by the same USER.ACCOUNT
identity as the child you're trying to kill.
--
Mark Bixby                      E-mail: [log in to unmask]
Coast Community College Dist.   Web: http://www.cccd.edu/~markb/
District Information Services   1370 Adams Ave, Costa Mesa, CA, USA 92626-5429
Technical Support               Voice: +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)

ATOM RSS1 RSS2