JNOS Commands Manual - The E Commands

The E Command Set

echo [accept|refuse]                              Default: accept

     Display or set the flag controlling client Telnet's response to a
 remote WILL ECHO offer.

    The Telnet presentation protocol specifies that in the absence of
 a negotiated agreement to the contrary, neither end echoes data received
 from the other. In this mode, a Telnet client session echoes keyboard
 input locally and nothing is actually sent until a CR is typed.

     Local line editing is also performed: backspace deletes the last
 character typed, while control-U deletes the entire line.

    When communicating from keyboard to keyboard the standard local
 echo mode is used, so the setting of this parameter has no effect.
 However, many timesharing systems (e.g. UNIX) prefer to do their own
 echoing of typed input. (This makes screen editors work right, among
 other things). Such systems send a Telnet WILL ECHO offer immediately
 upon receiving an incoming Telnet connection request.

     If 'echo accept' is in effect, a client Telnet session will
 automatically return a DO ECHO response. In this mode, local echoing
 and editing is turned off and each key stroke is sent immediately
 (subject to the Nagle tinygram algorithm in TCP).

    While this mode is just fine across an Ethernet, it is clearly
 inefficient and painful across slow paths like packet radio channels.
 Specifying 'echo refuse' causes an incoming WILL ECHO offer to be
 answered with a DONT ECHO; the client Telnet session remains in
 the local echo mode.  Sessions already in the remote echo mode are
 unaffected. (Note: Berkeley Unix has a bug in that it will still
 echo input even after the client has refused the WILL ECHO offer.
 To get around this problem, enter the 'stty - echo' command to the
 shell once you have logged in).




edit [<filename>]

     An ascii text editor is included the JNOS distribution.  A clone
of the UNIX "ed" editor, is invoked from the console with the path to
the file to be edited:

        edit   c:/ftpusers

     This option is enabled by compiling with EDITOR and ED #define'd.

     A full-screen console-only editor is available if JNOS is compiled
with both EDITOR and TED #define'd.




eol

    eol [standard | null]                           Default: standard

      Display or set Telnet's end-of-line behavior when in remote echo
  mode.  In 'standard' mode, each key is sent as is.  In 'null' mode,
  a NUL character is sent immediately after sending a CR.

      This command is not necessary with all UNIX systems; use it only
  when you find that a particular system requires two CRs to end a line.
  In any case, the eol setting is only pertinent when in remote- echo
  mode, since otherwise a CR is translated to LF by JNOS' tty driver.



errors [ON | off]

     Set whether the system will send messages about system errors and
 permission infringements to user 'sysop'.  Default is on.




etelnet <host> [<port_number>] loginid password

        The 'etelnet' command is similar to the telnet command (which
 see), but it accepts the login id and password to be provided to the
 <host> system.  The etelnet command is available when JNOS was
 compiled with MD5AUTHENTICATE #define'd.  Etelnet will encrypt the
 password if the <host> system supports MD5 authentication (as
 indicated by a [hex_number] challenge value in its password prompt).
 If no such challenge is provided, the password is sent "in the clear".

      If you are telnetting to a port/service that does not provide a
 password prompt, then 'telnet' should be used instead of 'etelnet'.



ettylink <host> [<port_number>] loginid password

     The 'ettylink' command is similar to the ttylink command ,
but it accepts the login id and password to be provided to the <host>
system should it request a login id and password.  The default port,
87, on a JNOS system does NOT request these, so using ettylink to this
port/application is not recommended.  The ettylink command is available
when JNOS was compiled with MD5AUTHENTICATE #define'd.  Ettylink will
encrypt the password if the <host> system supports MD5 authentication
(as indicated by a [hex_number] challenge value in its password prompt).
If no such challenge is provided, the password is sent "in the clear".



exit [return_code]                                  Default: 0

     Causes the JNOS program to terminate when at the JNOS> prompt.
When shelled to DOS, causes a return to the JNOS> prompt. When
terminating the program, an "Are you sure?" query is given. Enter "y(es)
<cr>" to end the program.  Any other response returns to JNOS.

     If a <return_code> numeric value is provided, this value
is returned to the caller of JNOS.  This is typically a batch file, which 
may then take action depending on this code.  For example: 
      ... 
:rerun 
      jnos110i-u1 -g2 
      if errorlevel 100       goto remote_exit 
      if errorlevel 99        reboot
      if errorlevel 1         goto rerun
      goto exit 
:remote_exit 
      ...
:exit


In this example, issuing "exit 99" would run the reboot command, "exit 1"
would restart JNOS, and "exit" or "exit 0" would exit the batch file that
invoked JNOS.  The remote command (c.v.) when given the exit parameter,
will use a return code of 100.




expire <subcommand>

     The 'expire' command is used to invoke the process which deletes
old BBS messages.  The mailboxes or newsgroups to be expired, and the
age (in days) after which a message may be deleted, are specified in
the Expirefile (defaults to /spool/expire.dat).


    expire [now | interval]

     Begin the expire process immediately, if <now> is specified,
     or every <interval> hours in the future (but no immediate
     expire is done). If no arguments are provided, the current expire
     interval is displayed.

         Example:  To run expire at 04:30 each morning, place these
         commands into your autoexec.nos file
                   at 0430 "expire 24" 
                   at 0431 "expire now"


Format of Expirefile:

#comment line 
mbox_name  number_of_days_to_retain_messages
mbox_path  number_of_days_to_retain_messages !news.group.name
number_of_days_to_retain_articles

If the number of days is omitted, 21 is used.  Also, if newsgroups
are specified, the associated History file is expired as well, but
the number of days used is the maximum of all the days provided for
newsgroups in the Expirefile.

     Example:  allusa 7
               amsat 10
               !swap 10 
               !rec.radio 7


See Also:  oldbid