On Mon, 7 Oct 2013, Cory Smelosky wrote:
On Mon, 7 Oct 2013, Cory Smelosky wrote:
On Mon, 7 Oct 2013, Brian Schenkenberger, VAXman- wrote:
Cory Smelosky <b4 at gewt.net> writes:
On Mon, 7 Oct 2013, Cory Smelosky wrote:
Let's assume you have no need for your prior accounting information...
$ SET ACCOUNTING/NEW_FILE/ENABLE=IMAGE
Execute the UUCP command(s) which fail.
$ ACCOUNTING/SINCE=TODAY
Post that output and let's see if there's anything revealing in there.
Also, you can $ SET ACCOUNTING/DISABLE=IMAGE because /ENABLE=IMAGE can
become a resource hog.
Doing so now.
I disabled TERM/INQ on login in SYLOGIN and the abort went away
(ACCOUNTING didn't have anything useful to say). I know I can disable it
per-line/per-use but this was the quickest test.
Now we're getting somewhere.
Try putting:
$ IF "''F$mode()'".EQS."NETWORK" THEN $ EXIT
at the beginning of your
SYLOGIN.COM and
LOGIN.COM files.
You can not SET TERM/INQUIRE if there's no terminal. ;)
It's coming in on a serial line, actually. Apparently that's not the problem
though as it's SYSTEM-ABORTing again...
Don't get why it works sometimes and sometimes not. I need Mark P's help for
this.
Weird. Despite the error UUCP seems to be working correctly.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects