The existing policy sets dirty_background_bytes to 5, which is erroneously
too small that incurs write amplification and read starvations.
Considering a raspi with 2 GiB of RAM, this is 43 million times smaller
than the default Linux policy, which is 10%.
Considering that this will be deployed to mostly read-only system with
emphasis on data integrity (hence needing tighter data writeback), set
this to 256 KiB.
Continuing addressing the overly excessive data writeback policies, also
bump the dirty_writeback_centisecs from 250ms to 1000ms. Any dirty data
written in the past 1 second will be written to the storage.
Signed-off-by: Juhyung Park <qkrwngud825@gmail.com>
* Fix crash on unload
Within main, exists a `window.beforeunload` handler which brings up the "Are you sure you want to close PiKVM session?" message. When the page is refreshed, the event is `undefined` and, the code which sets the `event.returnValue` to the aforementioned text provides an exception.
To reproduce:
1. Open KVMD web
2. Open developer tools to view Console.
3. Interact with the page by clicking the main window.
4. Refresh the page
5. Observe type error in console.
This patch checks if the event is defined before attempting to set the `event.returnValue`. Other functions are maintained.
* Add space
Second pull request for this bug. Apparently, in bash `cp -a <dir>/*` ignores dotfiles, which are often how authfiles get named, notably as per the documentation for SSL cert management for certbot plugins in the PiKVM Wiki. Using `cp -a <dir>/.` instead should catch dotfiles and all files and subdirectories correctly.
* Remove unused items
These items are called out as inactive or removed from pylint.
* Allow inspection of additional packages
By adding these package inspections, the pylint warnings are reduced. This brings us to a smaller list of items which do not comply with current PEPs. https://hackedyour.info/58KO86fiiL4wiV5r
* Lint problems discussed with lead
* Add comma to end of line
