📄 rfc431.txt
字号:
RFC #431 Mark KrilanovichNIC #13300 UCSBUpdates: 122 Dec. 15, 1972Obsoletes: 399 Update on SMFS Login and Logout This document replaces RFC 399, which introduced the Loginand Logout commands for UCSB's SMFS, but was incomplete. RFC 399is restated here, followed by a description of the nature of theresponse elicted by these commands Two new commands have been added to UCSB's Simple MindedFile System (SMFS). They are described below. Login (LGI) The Login command is the means whereby the user identifieshimself and specifies the account number to which his use of SMFSis to be billed. The user should issue a LGI command directlyafter completing the ICP and before any command referencing afile. The user name and account number specified remain ineffect until another LGI command is issued, a LGO command isissued, or the connection is close. At present, the use of SMFS is not billed, and thereforeuse of the accounting command is optional. It is requested,however, that users and user processes begin to use this commandas soon as possible, since we would like to collect statistics onSMFS utilization before implementing billing. Therefore, atpresent the user name can be any name that identifies the user,and the account number is completely arbitrary. The format of the LGI command is given below. Note thatthe lengths of the fixed-length fields are given in bits. The opcode for LGI is decimal 13. 8 <op code><user name><account number>The <user name> and <account number> fields are further divided [Page 1]NWG/RFC #431 MCK 15-DEC-72 12:39 13300Update on SMFS Login and Logoutas follows: 8 8*length <length><user name>Where <length> gives the length in 8-bit characters of the <username> or <account number> subfield. The maximum length of <username> is eight characters and of <account number> is fourcharacters. The <user name> and <account number> fields mustconsist of characters chosen from the same character set asfilenames. Logout (LGO) The logout command terminates the association between theuser and the accounting information specified in the last LGIcommand issued, if any; it does not cause SMFS to close theconnection. The user should then issue another LGI commandbefore attempting any operation referencing a file. It is notnecessary to issue a LGO command before issuing another LGIcommand, or before closing the connection. Again, at the present time the LGO command is optional,and does not affect the user's ability to reference files. The format of the LGO command is as follows: 8 <op code>The op code for LGO is decimal 14. Login and logout each elicit, as their only response, aneight-bit completion code. Like the other SMFS commands, thecompletion code is equal to the command's op code if the commandwas successful. The following error completion codes, given indecimal, are currently defined: 47 The length of <user name> is zero. 48 <user name> is too long. 49 <user name> contains invalid characters. 50 The length of <account number> is zero. [Page 2]NWG/RFC# 431 MCK 15-DEC-72 12:39 13300Update on SMFS Login and Logout 51 <account number> is too long. 52 <account number> contains invalid characters. 53 <user name) specifies an invalid user. 54 <account number> specifies an invalid account. [ This RFC was put into machine readable form for entry ] [ into the online RFC archives by BBN Corp. under the ] [ direction of Alex McKenzie. 1/97 ] [Page 3]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -