William Hubbs posted on Wed, 05 Aug 2015 10:26:33 -0500 as excerpted: > It isn't localmount that would have the issue, but mount.* because they > are lexically after localmount, so you would end up with localmount > doing a mount -a then mount.* coming later trying to mount file systems > again that were mounted by localmount.
But if localmount is a wrapper, then it pulls them in and they're already started (if they'll mount), just like they are now. You'd just have to have it still return success even if one of the wrapped mounts fails, in ordered to maintain compatibility. So coming later won't be a problem, if they're wrapped by localmount, because it will have already started them anyway, so they'll already be detected as started. Meanwhile, if localmount is not made a wrapper but continues to be mount -a, then you will indeed need logic in the individual mounts to see if they're already mounted, but a robust system will need that in any case, because there's simply too many reasons, including manual mounting, that they're already mounted. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
