driver / standard (pull_request) Successful in 15s
driver / lint (pull_request) Successful in 14s
driver / test (3.12) (pull_request) Failing after 46s
driver / test (3.13) (pull_request) Failing after 43s
driver / types (pull_request) Failing after 1m1s
driver / lowest (pull_request) Failing after 20s
driver / build (pull_request) Successful in 27s
driver / security (pull_request) Failing after 1m4s
CI / driver (pull_request) Failing after 2m16s
driver / publish (pull_request) Skipped
OpenMediaVault writes several cron files itself, from its own database, and writes them again on every apply: an edit napalm-linux made there would be taken back without a word. So every file OMV generates (/etc/cron.d/openmediavault-*, the mail-queue flush, apticron and the recycle-bin cleanup) is platform and only runs; the inherited writers refuse it. The web UI's "Scheduled Jobs" and the power-management schedule live in conf.system.cron.job. They are read through Cron.getList, disabled ones included, instead of the lines OMV generates for them, and switched with Cron.set, run with Cron.execute (followed through Exec.getOutput), made with Cron.set and removed with Cron.delete. An application's job on OMV is an OMV job, visible in its web UI, marked by its comment. Each write applies the cron module alone, so changes pending in the web UI for other modules stay pending. Every other job keeps napalm-linux's behaviour. Requires napalm-device-types 4.26.0 and napalm-linux 0.16.0. Closes #18