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

30
doc/user/logging.htm Normal file
View File

@ -0,0 +1,30 @@
<HTML>
<HEAD>
<TITLE>Logging your activity</TITLE>
</HEAD>
<BODY>
<H1>Logging your activity</H1>
<P>
SICS offers not less then three different ways of logging your
commands and the SICS server's responses:
<ul>
<li>The SICS command line client allows to open a log file on your
local computer and on your account. This can be achieved through the
File/Open Logfile menu entry. Select a file name and hit save. From
then on, any output in the SICS clients terminal area will be written
into the selected file. There is a gotcha: ouptut may not be immediately
visible in the file. This is due to buffering of I/O by the operating
system. If you want to flush, either open a new file or exit the
client. Flushing I/O at each line written is possible, but would have
a massive and unacceptable performance impact.
<li>You may create a similar per client log file on the computer running
the SICS server through the <a href="logbook.htm">logbook</a> command.
<li>Then there is a way to log all activity registered from users with
either user or manager privilege into a file. This means: all commands
which affect the experiment regardless from which client they have
been issued. This is accomplished with the <a href="commandlog.htm">
commandlog</a> command.
</ul>
</P>
</BODY>
</HTML>