You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 5, 2023. It is now read-only.
I've 4 cameras served by 4 instances of kerberos-docker (each writes into own sub-folder, i.e. /var/lib/kerberos.io/camX), and I noticed that some cameras have very less videos in the storage folder. I assume the reason is that I have 4 autoremoval instances running at the same time and depending on system load some may clean more files in its camera storage than others?
Is it possible to disable autoremoval code by, for example, checking for .noautoremoval file in this run.sh script?
Something like this:
I've 4 cameras served by 4 instances of kerberos-docker (each writes into own sub-folder, i.e. /var/lib/kerberos.io/camX), and I noticed that some cameras have very less videos in the storage folder. I assume the reason is that I have 4 autoremoval instances running at the same time and depending on system load some may clean more files in its camera storage than others?
Is it possible to disable autoremoval code by, for example, checking for .noautoremoval file in this run.sh script?
Something like this:
?
And then I'll write own script that will walk over all storages and do a clean-up, via cron or systemd timers.
The text was updated successfully, but these errors were encountered: