Skip the permission pass when it is right, and log command lines
The cleanup job wrote the user's grant on C:\msys2 on every run, which goes through all 30000 files and kept the only processor busy for half a minute every half hour. It is now only written when it is not there yet; a run takes 17 seconds instead of up to two minutes. Process creation events now carry the command line, so what a visitor ran is known even when they deleted their shell history along with the installation. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
b142a1c5d2
commit
3e1beb9994
1 changed files with 15 additions and 3 deletions
|
|
@ -106,7 +106,7 @@ made bigger as well, the security log to a gigabyte: the scanners of the remote
|
|||
megabytes of it in a week.
|
||||
|
||||
A start of the server that fails leaves nothing in that log. So windows records the history of the scheduled tasks
|
||||
and the start and end of every process, and when the server does not come up, the cleanup job writes the processes
|
||||
and the start and end of every process, with its command line, and when the server does not come up, the cleanup job writes the processes
|
||||
and the state of the server's task to `C:\ProgramData\kik-restore\failed-starts.log`.
|
||||
|
||||
Only keys may log in over SSH. The box stands in the open internet and both of its accounts have a password.
|
||||
|
|
|
|||
Loading…
Reference in a new issue