On Mon, Jan 03, 2011 at 01:15:17PM +0000, Simon Avery wrote: > Like many zoneminder users wanting to use a dedicated mount for cctv > storage, I replace /usr/share/zoneminder/events and images with > symlinks to the right place (ie, a bigger drive not in /usr)
/usr/share/zoneminder/events is a symlink to /var/cache/zoneminder/events in the package, though the same issue could come up for /var. what about mounting /var/cache/zoneminder/events directly (either on it's own filesystem, or using bind mounts), rather than mucking around with symlinks? > zoneminder upgrade silently deletes these symlinks and recreates the > original hard directories there. i believe this happens at the dpkg level, so might be hard or inappropriate to fix in zoneminder. > zoneminder then restarts and zmaudit can no longer find the associated > files so kills the events database entries. Result - total emptying of > zoneminder database and non-recovery of sorted events, including those > archived. > > Lost three weeks recordings (2tb) data from an entire site, plus archives > going > back for a year. :( ouch! this seems like a pretty severe way to handle all the files disappearing. will try and reproduce and see if there's a way to detect and avert this situation. just to be clear, it deleted the database entries for the recordings, and not the actual files? > Please include tests for symlinks and leave in place if found. while it certainly shouldn't purge cached data so unconditionally, i'm not sure what zoneminder can do when dpkg-managed symlinks and directories are changed manually. so i think we'd have to come up with some alternate method. live well, vagrant -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
