Posted on 07/15/2021 7:12:35 PM PDT by E. Pluribus Unum
Our elections are a wee bit more important than a router. AZ auditors don’t even have access to the routers yet so this log is inside a voting machine, scanner or tabulator. Like I said, storage is dirt cheap and tiny. Code to create multiple sequential files is easy. There’s no good reason to not store every bit of logs from start to finish in an election. I don’t think these logs were for troubleshooting but were for logging who accessed the system and when — activity log. Different situation.
Dominion was first designed to steal elections in Venezuela. Every design flaw is no flaw at all. They are by purposeful for cheating. Dominion employees were the only people who had admin access to be able to run a script and fill that log file with nothing useful.
There are several races across the country that could be affected by a 100k modification.
The vast majority of the incidences brought to light so far would be categorized as ‘loss of control’, which may or may not include provable fraud - but still plenty of reason for audits, questioning results, and in some cases overturning results. ‘Fraud’ is a much higher bar, as you have to prove WHY these things happened, and intent beyond that.
Also, keep in mind that a lot of these things have been described in terms which go beyond what is demonstrated or actually known. Some of these are likely explainable - but they must be explained, which to date they largely have not been. Some of these things seem unlikely to be explainable.
An example in regards the ‘deleted files’ issue in Arizona, is that the files appear to have been deleted as part of the ordinary process of moving the files to a different location...so the deletion itself is not fraud, nor even malfeasance. The issues there are that the files were not turned over as they are an essential part of the core record addressed by the subpoena, and that they were moved long after any reasonable explanation which has yet been provided - and contrary to statements the MCBE has made.
Let the log file increase to the capacity of the drive.
Usually you have a log on the device itself to allow convenient first-step troubleshooting. As noted in a previous post, for Cisco devices that is (an inadequate) only 4kB as a default. The log files sizes are also large enough that if communications to the server are cut off for a time that enough records to troubleshoot are kept within the device itself. Major storage is sent to another server - which is why they want the Splunk data. https://en.wikipedia.org/wiki/Splunk
Splunk is an off-device application which collects these alerts and logs, and allows for long term storage (I’m told often a years worth of logs but can be longer if retention requires), and the ability to readily search, display, and graph/chart the data.
There’s no good reason to not store every bit of logs from start to finish in an election.
As for the device’s log size, it usually competes with all the other uses for memory, so there are tradeoffs between logging and those other uses. You don’t ever want to use all available memory. Some communications devices erase those logs entirely every time they restart, so that they exist at all here on devices which have been turned off, and are 20MB in size, is rather good. Again, this is just the local copy.
Enough evidence to recall Electors.
It has begun
.
.
What has begun?
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.