JNOS Commands Manual - The F Commands
The F Command Set
finger <username[@host]> [<username[@host]> ...] Issue a network 'finger' request for <username> at <host>. Finger is typically used to find out specific information about users on local or remote hosts. By fingering a user, you can find out such information as a user's name, his mailing address, telephone number, QSL information, and other useful facts. This information is kept in a separate text file for each user. As our network expands, this application will help hams find out information about each other quickly and efficiently. The finger command under NOS can be issued in any of the following three ways: finger <username> >> Examples: finger n8fow finger <username>@finger n8fow@n8fow finger @<host> finger @n8fow The first form of the command is used to find out information about a user at the local host, namely your own system. It is useful for testing 'finger' on a system that you know is running. The second form of the command is used to find out information about a user at a remote host. If you don't know the name of a particular user at a remote host, you can use the third form of the command. This command returns a list of all 'finger' files on the remote system. To enable the finger server so that others may query the users on your system, you must give the 'start finger' command. The finger files that provide information on a <username> are located by default in \finger (see Fdir and Fdbase in nos.cfg), and are ordinary ASCII files created by the sysop. Also, if the SAM or QRZ callbook server is configured, <username> is looked up in the callbook and displayed if the search is successful. Certain <username> strings are taken to mean that a JNOS function should be invoked to display system information, depending on what configuration options were used to build the server JNOS: <username> config_opt output_same_as conf CONVERS conference bridge /WHO links CONVERS conference bridge /LINKS mbxinfo MAILBOX 'I cmd in mailbox' mhold HOLD_LOCAL_MSGS 'mbox holdlocal' mstat MAILBOX 'mbox mailstat' mpast MAILBOX 'mbox past' users MAILBOX 'mbox status' usersdat USERLOG 'finger x' forall users in users.dat mailfor MAILFOR 'mbox mailfor' info ALLCMD 'info' ax25 AX25 'ax25 stat' aheard AX25 'ax25 heard' netrom NETROM 'netrom stat' iheard all 'ip heard' memstat all 'mem stat' socket all 'socket' tcpview all 'tcp view bytes' asystat ASY 'asystat' pkstat PACKET 'pkstat' rip RIP 'rip stat' fkey The 'fkey' command allows you to program the function keys and several other cursor control keys. fkey This command produces a listing of the currently defined function keys. fkey <key_number> [<value> | "<string>" ] Display or define a new setting for a function key. Control characters can be included in the string by prefixing with the ^ character (SHIFT 6 on most keyboards); e.g. CR is entered as ^M. To insert a ^ in the string, enter ^^. Note: If the first character of a function key definition is '~' then JNOS switches to the Command session and processes the rest of the definition (if any). >> Examples: fkey 87 "trace tnc0 211^M" (SHIFT-F4 turns trace on) fkey 72 "" (disable up arrow) fkey 113 "~" (Alt-F10 switches to the Command session) FKEY TABLE key num def. key num def. key num def. key num def. Stab 15 F1 59 CF2 95 CF3 96 F2 60 F3 61 CF4 97 CF5 98 F4 62 F5 63 CF6 99 CF7 100 F6 64 F7 65 CF8 101 CF9 102 F8 66 F9 67 CF10 103 AF1 104 F10 68 home 71 ^H AF2 105 AF3 106 up 72 ^[[A pgup 73 ^U AF4 107 AF5 108 left 75 ^[[D right 77 ^[[C AF6 109 AF7 110 end 79 ^E down 80 ^[[B AF8 111 AF9 112 pgdn 81 ^J ins 82 ^A AF10 113 Cprnt 114 del 83 ^? SF1 84 Cend 117 Cpgdn 118 SF2 85 SF3 86 Chome 119 Cpgup 132 SF4 87 SF5 88 F11 133 F12 134 SF6 89 SF7 90 SF11 135 SF12 136 SF8 91 SF9 92 CF11 137 CF12 138 SF10 93 CF1 94 AF11 139 AF12 140 ftp <hostname> [<scriptfile>] The ftp command is used to make a TCP connection with <hostname>, and then use File Transfer Protocol to exchange data between the systems. Once the connection is established, a small set of commands is used to manage the file exchange. A command is executed locally if it is a local client command. Otherwise, the command is sent to <hostname> for execution. If <scriptfile> is provided, all commands are obtained from the indicated file; otherwise, they are read from the console. The following are commands supported by JNOS clients and servers: ? Display all available command names. ascii Treat the data to be transferred as ASCII text, so that line endings are used suitable to the receiving system. batch [y|n] Query the state of the command batching flag, or set it if <y|n> is given. Batching involves sending as many commands as possible before waiting for responses from <hostname>. binary Treat the data to be transferred as binary data, that is, verbatim data not to be changed while storing on the receiving system. cd path Change to directory <path> on system . cdup Change to immediately-superior directory on system <hostname>. dele file Delete <file> on the remote system. dir spec List the contents of the current directory on the remote system, in a verbose manner. If <spec> is given, the subset that matches this file specification is listed. Example: dir *.exe get file Transfer <file> from remote system TO the local system. hash [y|n] Query the state of the hashmark flag, or set it if <y|n> is given. Hashmarks are written to the screen for each 1000 bytes written to the local file system. help Same as ? lcd path Change to directory <path> on the local system. ldir spec Same as the dir command, but applied to the local system. list Same as dir command. lmkdir dir Create directory <dir> on the local system. ls spec List just the names in the current directory on the remote system. If <spec> is given, the subset that matches this file specification is listed. Example: ls *.exe mdtm file Display the modified-time in GMT for <file> as yyyymmddhhmmss. mget spec Transfer all files matching <spec> from the remote system TO the local system. mkdir dir Create directory <dir> on the remote system. mput spec Transfer all files matching <spec> to the remote system FROM the local system. nlst Same as ls command. put file Transfer <file> to the remote system FROM the local system. quit Close the TCP connection to <hostname> and exit the ftp cmd. See also the JNOS "abort" command. reclzw [y|n] Query the state of the ftp client LZW-supported flag, or set it if <y|n> is supplied. LZW compression is only supported for ASCII-type transfers. rename from to Rename the file named <from> to the name <to> on the remote system. reget file The RFC959-endorsed way to restart an interrupted get. No check is made to assure the file is consistent between systems; the size of the local <\ is provided to the remote system and a get is issued relative to this point. restart pos The RFC959-endorsed way to restart a transfer is to first establish a starting offset position and then issue a transfer command to resume at that position. The dir command would be useful to obtain the offset to specify in the restart command, and then a put <file> would cause <file> to be sent starting from the given position. resume file Restart an interrupted transfer of <file> from the remote system to the local system. Checks are made to assure the file is consistent between systems. This is a JNOS extension to the FTP standard. Other non-compatible equivalents exist in other implementations (c.f. wu-ftpd). rmdir dir Delete (remove) directory <dir> on the remote system. rput file Resume an interrupted transfer of <file> to the remote system FROM the local system. Checks are made to assure the file is consistent between systems. This is a JNOS extension to the FTP standard. Other non-compatible equivalents exist in other implementations (c.f. wu-ftpd). sendlzw [y|n] Query the state of the ftp server LZW-supported flag, or set it if <y|n> is supplied. LZW compression is only supported for ASCII-type transfers. type [a|b|l] Query the current transfer type value, or set it if <a|b|l> is given. Use <ascii>, <binary> (or <image>). <logical 8> is also supported. view file Transfer <file> from the remote system TO the local system's console screen. The file is assumed to be an ASCII file! verbose [n] Query verbosity of error handler, or set it if integer <n> is given. 0 => error msgs only, 1 => final msg only, 2 => control msgs too, 3 => control msgs + hash marks, 4 => control msgs + byte counts. Since unrecognized commands are sent to the remote ftp server for evaluation, additional commands may be available, depending upon the ftp server implementation. For example, the WU-FTPD may accept site- written extensions, and thus allow: site exec <extended_cmd> <cmd_args>. The remote ftp server will require a login name and password. These values may be provided by a file called "net.rc" by default (see Hostfile in nos.cfg). The file has entries in this format: remote_hostname login_name password but password may be omitted to instead have the client ftp prompt for it. Many systems, including JNOS, will reduce the amount of extraneous messages sent, if the password is prepended with a '-'. However, JNOS does not support this when an anonymous login occurs via an MD5 authentication exchange.
(Courtesy KBNorton Computer Services)