Subject: | |
From: | |
Reply To: | |
Date: | Fri, 24 Oct 2003 11:38:16 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
(Running MPE/iX 6.0 pp2,) I start up inetd like this:
!job jinetd, manager.sys;outclass=lp,1
!comment the config file is /etc/inetd.conf or INETDCNF.NET.SYS
!comment
!comment some ways to interact with inetd (requires SM)...
!comment run inetd.net.sys;info="-k"
!comment where -k=kill; -c=config-file re-read; -l=logging(toggle)
!
!run inetd.net.sys;PRI=CS;info="-l"
!CONTINUE
!showjcw
!CONTINUE
!setvar mycierror cierror
!tell tracy,manager.sys inetd exiting with cierror !mycierror
!IF mycierror <= 0
! SET STDLIST=DELETE
!endif
!eoj
I thought I was turning on connection logging by including the -l, but nooo,
issuing a subsequent interactive inetd.net -l causes a 'logging enabled'
message to appear, so I have to assume that the initial with-parm invocation
doesn't turn it on.
Anyway, I need a smarter jobstream, so I'm hoping somebody's already written
it.
(redface, I just realized that while leaving jinetd running during the
backup works great, making sure it's up by streaming this jinetd again is
toggling the logging, not exactly what I want.)
Is there a way to determine the present state of logging? (other than
looking at the stdlist back-to-front?) Or maybe there's a way to turn it on
via the config file?
Tracy Pierce
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|