On Tue, 2011-01-04 at 14:44 -0800, Vagrant Cascadian wrote: > On Tue, Jan 04, 2011 at 06:55:50AM +0000, Simon Avery wrote: > > Thanks for the reply! > > of course! >
And sorry for my slow reply . . . my mailserver has been broken for some days, only got the flood of correspondence this morning. > > > 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? > > > > > > Perhaps a better way would indeed be to set the path in config, but > > zoneminder's path config is relative to its home dir, so ../../ to ascend to > > root and then to your mount of choice might get complicated (unless I've > > misunderstood it) > > it doesn't look easily supportable that way, at least to me. > It's not. I looked at that in 2006, and it needs significant changes upstream to make that work. I don't think the main developer is against it, it's just never been a high priority. > these lines in fstab could allow you to bind-mount an alternate location: > > /dev/sdX1 /otherdrive ext3 defaults 0 2 > /otherdrive/zoneminder/images /var/cache/zoneminder/images bind defaults 0 2 > /otherdrive/zoneminder/events /var/cache/zoneminder/events bind defaults 0 2 > > or if you have a separate partition for each: > > /dev/sdX1 /var/cache/zoneminder/images ext3 defaults 0 2 > /dev/sdX2 /var/cache/zoneminder/events ext3 defaults 0 2 > > > > If it is more of a case of changing mounts in a different way, and if it's > > going to be hard to fix in the upgrade, then I'm happy to change my ways and > > update zoneminder's wiki on the subject over at > > http://www.zoneminder.com/wiki/ > > index.php/Using_a_dedicated_Hard_Drive > > i can confirm that the symlinks got replaced on upgrading from 1.24.2-6 to > 1.24.2-7, as well as on re-install of 1.24.2-7 the package. given your bug > report, that wiki page does seem like a dangerous recommendation; please > update > it! i think directly mounting or bind-mounting would be a much safer > approach. > > i don't think zoneminder is doing anything unusual with those symlinks, > they're > just part of the package. zoneminder could detect non-default/unknown symlink > locations in the preinst script, and fail to upgrade in those cases; not > pretty, but maybe better than loosing the database data. > In the short term, I don't think there's a neater solution than that. I think we should go with the "bail out update with warning" approach. We should also add the above mount info to README.Debian > > someone else noted on this bug report that /var/cache/zoneminder isn't really > the right place either... which i also remember thinking when i started > helping > with zoneminder maintenance, but that will probably have to wait till > squeeze+1 > (unless that too is deemed RC). > > I'll raise a separate bug for that. > live well, > vagrant > -- Peter Howard <p...@northern-ridge.com.au> -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
