- fixed a little bug with hkl: phi limits were not properly tested
- updated powder file writing to properly work with mean and stddev
This commit is contained in:
@ -7,7 +7,8 @@
|
||||
<P>
|
||||
The commandlog is a file where all communication with clients
|
||||
having user or manager privilege is logged. This log allows to retrace each
|
||||
step of an experiment. This log is usually switched off and must be
|
||||
step of an experiment. This log is normally configured in the startup
|
||||
file or can be
|
||||
configured by the instrument manager. There exists a special command,
|
||||
commandlog, which allows to control this log file.
|
||||
<DL>
|
||||
@ -27,6 +28,10 @@ Log files are written to the log directory of the instrument account. There
|
||||
<DT>commandlog tail n
|
||||
<DD>prints the last n entries made into the command log. n is optional and defaults to 20. Up to 1000 lines are held in an internal buffer for this command.
|
||||
</DL>
|
||||
It is now possible to have a script executed whenever a new log file is
|
||||
started. In order to make this work a ServerOption with the name logstartfile
|
||||
must exist in the instrument configuration file. The value of this option
|
||||
must be the full path name of the file to execute.
|
||||
</P>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
Reference in New Issue
Block a user