
remote [-p <port>] [-k <key>] [-a <kickaddr>] <host> kick | exit | reset

        Send a UDP packet to the specified host commanding it to exit
        NOS, reset the processor, or force a retransmission on TCP
        connections.

        For this command to be accepted, the remote system must be
        running the remote server.  Also, the port number specified in
        the remote command must match the port number given when the
        server was started on the remote system.

        If the port numbers do not match, or if the remote server is not
        running on the target system, the command packet is ignored.

        Even if the command is accepted there is no acknowledgement.

        The 'kick' subcommand forces a retransmission timeout on all TCP
        connections that the remote node may have with the local node.

        If the '-a' option is used, connections to the specified host are
        kicked instead.  No key is required when using the 'kick'
        subcommand.

        The 'exit' and 'reset' subcommands are mainly useful for
        restarting NOS on a remote unattended system after the
        configuration file has been updated.  The remote system should
        invoke NOS automatically upon booting, preferably in an infinite
        loop.


        remote -s [<key>]
          The 'exit' and 'reset' subcommands of 'remote' require a
          password.  The password is set on a given system with the '-s'
          option, and it is specified in a command to a remote system with
          the '-k' option.

          If no password is set with the '-s' option, then the 'exit' and
          'reset' subcommands are disabled.

          Note that 'remote' is an experimental feature in NOS; it is not
          yet supported by any other TCP/IP implementation, although a
          version of the remote command for BSD Unix exists.



