more about date specifications that can be used in filters:
http://www.gnu.org/software/tar/manual/ ... r_113.html
should this be added to wiki as it took for me some code browsing to realize the way it works?
Enable Purge when full by default
good deal (that's what they say in alabama)
maybe you can remove last paragraph about UTC, that might confuse someone.. besides some ZM users already had problems with their system clock set to UTC (just because php by default ignores system tz settings) and that last paragraph could make things even worse.
maybe you can remove last paragraph about UTC, that might confuse someone.. besides some ZM users already had problems with their system clock set to UTC (just because php by default ignores system tz settings) and that last paragraph could make things even worse.
if common sense is so uncommon, why is it called common then?
The system must be able to handle a full disk by default. My first Zoneminder install (about a year ago) died when the disk got full. Since then I've configured the PurgeWhenFull filter properly. I'm not sure why you're seriously debating whether or not this should be turned on. Let me break things down as I see them.
1. If you don't leave a small amount of space free linux breaks.
2. New events are more important than old events.
The solution is to automatically delete the oldest event to make room for a new event. If you don't want an old event to be deleted, it can be archived.
1. If you don't leave a small amount of space free linux breaks.
2. New events are more important than old events.
The solution is to automatically delete the oldest event to make room for a new event. If you don't want an old event to be deleted, it can be archived.
You missed out:
0. System Administration Rule #4: Never share a partition between core system and data files, as a runaway process creating the latter can leave no room for the former and hence bring the whole lot down (as you found out). This doesn't just apply to ZoneMinder events, but mail queues, log files, etc (hence why it is considered best practice to have /var on its own partition).
The reason this issue it is being debated is because, as always, there are (at least) two viewpoints and hence two perspectives as to what the default behaviour should be. Neither is necessarily right or wrong.
Incidentally I disagree with your second point - new events are not necessarily more important than old ones... e.g. your house gets burgled and the thieves get away but were caught on camera - a nosey neighbour hears the comotion and comes round to check your property completely unaware that they are being recorded on camera. The disk fills up and starts deleting old events. Your evidence gets deleted, but at least you've got some shots of your neighbour tidying up...
Mathew
0. System Administration Rule #4: Never share a partition between core system and data files, as a runaway process creating the latter can leave no room for the former and hence bring the whole lot down (as you found out). This doesn't just apply to ZoneMinder events, but mail queues, log files, etc (hence why it is considered best practice to have /var on its own partition).
The reason this issue it is being debated is because, as always, there are (at least) two viewpoints and hence two perspectives as to what the default behaviour should be. Neither is necessarily right or wrong.
Incidentally I disagree with your second point - new events are not necessarily more important than old ones... e.g. your house gets burgled and the thieves get away but were caught on camera - a nosey neighbour hears the comotion and comes round to check your property completely unaware that they are being recorded on camera. The disk fills up and starts deleting old events. Your evidence gets deleted, but at least you've got some shots of your neighbour tidying up...
Mathew
Yes it does tell in the manual and Yes people should read it.
and this debate was actually over a few months back, Just the thread got reawakened, Thanks W.
It will not be enabled by default since when setting up a system it has to be configured. That might include changing the events path, which someone could inadvertently put a wrong path that could lead to other files (making such a mistake with the filter enabled would have the purge scripts remove all files/folders not events related or in the database) so there for, enabling it is considered part of the configuration.
and this debate was actually over a few months back, Just the thread got reawakened, Thanks W.
It will not be enabled by default since when setting up a system it has to be configured. That might include changing the events path, which someone could inadvertently put a wrong path that could lead to other files (making such a mistake with the filter enabled would have the purge scripts remove all files/folders not events related or in the database) so there for, enabling it is considered part of the configuration.