Replies

20mb is insane. It’s the equivalent of one high resolution picture from a decent digital camera. They make 64gb(65,000+mb) MicroSD cards the size of a thumbnail.

I’ve opened 50mb text files and it was a bit of a struggle for my various text editors. Sublime code editor handled it the best. I can possibly see limiting a single log file to that size but it’s super basic to write the code to save a log file and start a new one at a certain size. My WordPress websites do that.

There’s no good reason to have one single 20mb log file, unless your plan is to be able to wipe it easily with a script to cover your tracks.

Dominion people are complicit.

Right. Of course, that likely is configurable, and space is cheap.

Trying to keep my mind open, under normal circumstances I would assume poor software design by a vendor, and would send them a suggestion that, by default, they make them 250 MB or something like that.

But I also try to remember that logging in various systems is highly variable. Some logs are so verbose that is is really hard to sift through them, and logs from another vendor are so sparse and poorly laid out that that they are utterly worthless. I have had lots of conversations about medical system logs when trying to figure out why something failed, that you say to the vendor:

“Look. I am glad you show the date and time the software opened and what the version is at that time in your logs, but...you don’t log who opened and closed a specific patient file! What good is that???” (cue indignant and frustrated voice)

What is really frustrating is the logs that are really verbose and cluttered, but contain very little useful information.

There’s no good reason to have one single 20mb log file, unless your plan is to be able to wipe it easily with a script to cover your tracks.

A lot of network equipment works that way, since its purpose is troubleshooting recent events. 20MB is usually plenty, since the information is single lines of text, and many systems use encoded versions of that even which simply store the timestamp, the event type, and the interface or address to what it pertains, but will display a text version when you pull it up.

A Cisco router default log:

“The typical default size of a router’s logging buffer is 4,096 bytes (although some high-end routers will default to a higher value). A buffer of this size can hold approximately 50 log messages before overwriting occurs. Fifty messages, although better than no logging, is relatively small, and most engineers will want increase their buffer size to store more messages”