I have D3 running on Windows 2000. Connections are most always made to the
server from a client PC using telnet.

When users log off, a new "login please" prompt appears, and the telnet
program remains active since the connection to the server still exists. I
know that there is a way to have the D3 telnet server end the session, which
will then cause the telnet client application to close. But I can't
remember what is required to make this happen.

Needless to say, I would appreciate any advice on the subject.

thanks in advance

Brian,

You can issue the EXIT command instead of the OFF command.

This will disconnect the telnet session, and if you have AccuTerm,
you can also make sure that it closes AccuTerm.

Larry Hazel

"Brian Bond" <brian (AT) XYZXYZXYZXYZbonanzapress (DOT) com> wrote

Look at the DCD-ON verb, we used this on D3/Unix and it logs off the
terminal when the DCD signal disappears.

I'm not sure if this is what you are looking for but I hope it helps.

Regards,

Neil.

"Brian Bond" <brian (AT) XYZXYZXYZXYZbonanzapress (DOT) com> wrote

That did the trick. Thanks much.



"Homer L. Hazel" <hNoOmerlhANTI (AT) SPAMcox (DOT) net> wrote

Funny, when I issue the EXIT command, I get an error message

"[3] The verb 'disc' is not defined."

If I edit the MD EXIT, it says

001 n
002 disc (f

This is on D3/NT 7.4.4

Sholom


Homer L. Hazel wrote:

Do you have an MD entry for "disk"?

Ours looks like this:

:ED MD DISC
top
..P

001 VR
002 3]9
003 F
004 dm,bp, disc




"SH" <shamada (AT) prupipe (DOT) com> wrote

"SH" wrote
001 VD
002 17
as the dm,md, DISC verb. If that works ok for you, you
can copy it to that other account you had been using, or
{from dm} do UPDATE-MD that-account-of-yours
<<tell it no when it offers to make user item(s) from each account>>
when update-md finishes that account and prompts for next MD,
hit enter to exit update-md.

Woops. I do have the proper MD DISC in my DM account, but in our user
accounts DISC is defined as a file. Seems that pre-D3 (i.e Ultimate), we
had a file definition DISC (for DISCOUNTS) in our user accounts. I guess
when we went over to D3, it allowed that file definition to remain.

I'll copy the DISC verb defintion to another name and see what happens.

Sholom

Frank Winans wrote:

Sounds like you're either not running update-md or not checking the
output as it's displayed. This can easily happen when going through
release update instructions and not really watching the screen.

The update-md verb will warn you:
File definition 'abc' not overwritten.
For items that are replaced by update-md you will be warned:
Item 'abc' overwritten - copied to CLASHES,acctname file
There is no output when there are no clashes.

I don't suggest this as a benign operation for all sites or especially
for production accounts, but... You could run update-md on all
accounts (except dm!) and capture the output to see what is not
updated, then fix each anomaly as required. That will avoid similar
issues in the future.

T


Sholom wrote: