can't restart with mounts in use

[Dave Love]

If the am-utils init script is used to restart amd when
a mount is in use (e.g. a home directory) it hangs
and leaves the mounts in a mess. This happens
in my case on an upgrade, since my home directory
is mounted by amd, and I do the upgrade from that
account, but also on a shutdown (which means it
takes ages waiting unsuccessfully for amd to die.

This is in edgy (package 6.1.5-1). I used to run a
similar setup under Debian sarge (amd 6.0 something,
I think) without such a problem, so I assume this is
a difference in behaviour between the 6.0 and 6.1
versions.

[Lionel Le Folgoc (mrpouit)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

[Dave Love (fx-gnu)]

Lionel Le Folgoc <email address hidden> writes:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Thanks in advance.

Yes, it is. I currently have version 6.1.5-6 installed, which I guess
was the latest from Debian when I looked after find the problem
persisted in Feisty. It isn't enough of a problem for me to spend the
time to debug it, especially as that's disruptive to do.

[Tim Cutts (timc)]

I'm not sure there's much that can be done about this - it's the nature of am-utils that it can't be restarted cleanly if mounts are in use (autofs behaves similarly; I suspect this is something that always tends to be the case with automounters). I suppose I could always just change the postinst script so that it does not attempt to restart the automounter on upgrades, but that might open a whole new can of worms.