How do you try to copy Windows NT's Event Log — which is essentially unchanged from the 1990s when systems ran on 32MB of RAM or less — and fail so spectacularly?
The first thing I do on a Linux system is install a proper syslog daemon.
How do you try to copy Windows NT's Event Log — which is essentially unchanged from the 1990s when systems ran on 32MB of RAM or less — and fail so spectacularly?
The first thing I do on a Linux system is install a proper syslog daemon.
One of the first things I do on win10 is disable most of excess logging.
But why, though? I have never seen a performance hit from it that would warrant that.
Dont like SSD wear for no reason. I wont look at those logs anyway on my personal gaming pc so its all useless.
Your issue is greatly exaggerated.
Enterprise users increase the logging and I've never heard of premature SSD failure due to this. The event log is capped in size (adjustable). It's nominally < 100MB.
Your games continually dumping GBs of data into local cache on the other hand...
Size cap doesnt mean much when its a constant stream of small writes.
How do you do that?
Painfully and slowly clicking one item at a time in computer management/event viewer/windows logs/applications and services :|
Im sure this can be automated, but I want to see what Im disabling instead of going bulk all.
https://utcc.utoronto.ca/~cks/space/blog/linux/SystemdJourna...
"The systemd journal doesn't force you to not have plain text logs" -- Chris Siebenmann (2024-06-30)
Which log daemon do you use?
syslog-ng FTW! Been using it since like 2003. Great router tools in the conf, network support, crazy regex rules for when you're trying to tune your syslog collector system after a few beers. Even has this awesome (footgun?) feature that lets me pipe matching lines to other tools I wrote (also beer influenced).