Hi Carl,
Thanks for your bug report.
This is indeed a sensible feature request, and your suggested fix
is a workable solution. My slight reservation is that 'cryptmount -ua'
will only deal with targets that are listed in /etc/cryptmount/cmtab
(ignoring any created via the --config-fd option), and will complain
about targets that weren't mounted at all.
I'll have a think about whether there's any neater way
of getting round the issue you've identified. This may have to wait
for a future (?minor) release of the upstream package.
Thanks,
RW Penney
+-- on Thu, Apr 19, 2007 at 02:50:55PM -0400, Carl Banks wrote: ---+
> Package: cryptmount
> Version: 1.2-1
>
> Hi: this is a wishlist item. I use cryptmount with a loopback drive
> that is NOT automounted at boot (that is, it is not listed in
> /etc/default/cryptmount). I manually mount and umount it as necessary.
>
> However, the Debian shutdown scripts fail to umount it, which in turn
> prevents the root partition from being umounted, which in turn causes an
> fsck on the next boot.
>
> Perhaps it's a bug in initscripts. Regardless, it'd be nice if
> /etc/init.d/cryptmount could optionally run "cryptmount -u -a" to umount
> any manually mounted cryptmounts, or at least allow for targets that are
> automatically umounted though not automatically mounted.
>
> Thanks
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
