linse/sics
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial revision

Browse Source
This commit is contained in:
cvs
2000-02-07 10:38:55 +00:00
commit fdc6b051c9
846 changed files with 230218 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
doc/user/token.htm Normal file
View File

@ -0,0 +1,35 @@
<HTML>
<HEAD>
<TITLE>The Token Command</TITLE>
</HEAD>
<BODY>
<H2>The Token Command</H2>
<P>
In SICS any client can issue commands to the SICS server. This
is a potential cause for trouble with users issuing conflicting
commands without knowing. In order to deal with this problem a
token mechanism has been developed. A connection can grab a
token and then has full control over the SICS server. Any other
connection will not be privileged to do anything useful, except
looking at things. A token can be released manully with a
special command or is automatically released when the connection
dies. Another command exists which allows a SICS manager to
force his way into the SICS server. The commands in more detail:
<DL>
<DT>token grab
<DD> Reserves control over the instrument to the client isssuing this
command. Any other client cannot control the instrument now. However, other
clients are still able to inspect variables.
<DT>token release
<DD> Releases the control token. Now any other client can control the
instrument again. Or grab the control token.
<DT>token force password
<DD>This command forces an existing grab on a token to be released. This
command requires manager privilege. Furthermore a special password must be
specified as third parameter in order to do this. This command does not grab
control though.
</Dl>
</P>
</BODY>
</HTML>