There's a reference to the issue in:
http://lists.freedesktop.org/pipermail/hal/2004-September/001042.html
comment:
+++ ./hald/hald_conf.h 2004-09-22 23:06:42.000000000 +0100
+ /** If true, then the behaviour of hald matches the use of
+ * autofs (automount - /etc/auto.hal) instead of a static
+ * fstab expectations.
+ *
+ * Basically it doesn't keep on generating mount notifications
+ * just because autofs automatically unmounts a volume, which
+ * would get _excruciatingly_ boring for users when the autofs
+ * timeout is set to oh, say, two seconds.
+ */
changelog:
- added new config option "autofs_in_use" to hald.conf please think of a
better name!
Possibly also handled by:
hal (0.5.7.1-1) unstable; urgency=low
* debian/patches/16_dont_stat_autofs.patch:
- Added. Don't stat autofs filesystems as that will remount.
(Closes: #361785) (From upstream git)
** Bug watch added: Debian Bug tracker #361785
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361785
** Also affects: hal (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361785
Importance: Unknown
Status: Unknown
** Changed in: autofs (Ubuntu)
Status: New => Invalid
--
hal interferes with umount autofs using SIGUSR1
https://bugs.launchpad.net/bugs/63720
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
