Skip to content
Snippets Groups Projects
Commit 4e9c9626 authored by Niko Ehrenfeuchter's avatar Niko Ehrenfeuchter :keyboard:
Browse files

Update README about the "var/" directory.

Fixes to #5
parent 856d8e10
No related branches found
No related tags found
No related merge requests found
......@@ -149,10 +149,11 @@ don't have one, and none of the other ActiveDirectory setups known to us have on
either, the service places its log messages in a plain text file in good old
Unix habits.
Everything that needs attention is written into the service's base directory in
a file called `AutoTx.log`. The contents of the log file can be monitored in
real-time using the PowerShell command `Get-Content -Wait -Tail 100 AutoTx.log`
or by running the [Watch-Logfile.ps1](Scripts/Watch-Logfile.ps1) script.
Everything that needs attention is written into a file called
`<HOSTNAME>.AutoTx.log` in the `var/` subdirectory of the service's installation
directory. The contents of the log file can be monitored in real-time using the
PowerShell command `Get-Content -Wait "$($env:COMPUTERNAME).AutoTx.log"` or by
running the [Watch-Logfile.ps1](Scripts/Watch-Logfile.ps1) script.
The log level can be set through the configuration file.
......@@ -161,7 +162,7 @@ The log level can be set through the configuration file.
Same as for the log messages, the service stores its status in a file, just this
is in XML format so it is easily usable from C# code using the core
Serialization / Deserialization functions. Likewise, this file is to be found in
the service base directory and called `status.xml`.
the `var/` directory and called `status.xml`.
### Grace Location Cleanup
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment