On Tue, Jan 31, 2012 at 5:25 PM, Kevin Chadwick <ma1l1ists@yahoo.co.uk> wrote:
On Tue, 31 Jan 2012 13:50:27 +0100 Tom Gundersen wrote:
udev should never, ever mount stuff itself. This is dangerous and explicitly not supported. Consider using systemd, udisks or another daemon for this purpose. For more info about this, see the recent discussion on the linux-hotplug mailinglist.
Are you referencing the 30 second timeout that Sanders link pointed to?
It su's to a normal user and runs a script which uses sudo and only applies to usb ports. I'm fairly sure but not certain that that wouldn't hold up udev? Interestingly I can't imagine a device taking 30 seconds to mount. Atleast if it was a usb I'd pull it out and try again after 15 seconds.
The time it takes to mount depends on a lot of factors, but that's not really the problem. A solw mount will not affect udev, the problem is that udev is not meant to manage disks. E.g. who is making sure the disk is unmounted before it is unplugged (yanking it out whilst mounting/fsck'ing does not sound like a good idea btw)? udisks is designed for this purpose, so I suggest using that. It uses udev to get events about plugged in devices (which is what udev is meant for) but does the mounting/monitoring/unmounting itself. I guess the udev page on our wiki should be "pruned" a bit so we don't give people bad advice (on my TODO). -t