Hi,

Laurent Bercot wrote on 29/07/2015 at 17:34 CEST:
> On 29/07/2015 17:07, tilt! wrote:
>
>> I am certain there is a way of solving this "automounting
>> problem" (if I may call it that) cleanly, without the use
>> of either of them. :-)
>
> There is a way to solve (almost) every suid issue
> cleanly, but it requires running a small additional
> daemon for every command you might want to run with
> special privileges, so this is not a generic solution
> - but it can work for automounting.
>
> http://skarnet.org/software/s6/s6-sudo.html

The daemon-based solution has its upsides:

(1) One problem / One program => "do one thing right".

(2) Indirection via an entangled policy management
     service or a possibly omnipotent commandline is
     avoided.

(3) System behavior of automounting was easily enabled
     and disabled per "service automount start/stop".

My estimate is that such daemon was not resource hungry:
We are talking automounting on manual hotplug, with a
latency in the seconds, so a 1s polling interval was more
than sufficient. We are talking device changes maybe every
few minutes (on busy days), so it does not have to buffer
many requests either. We are talking single-user, so even
with management of an idle-umount policy there is not
much state to take care of.

That is, of course, unless someone finds it should also
do automounting of network file systems, possibly on a
mobile, roaming device, from flimsy "cloud services";
then things could get ugly fast ... but that is not what
we're talking about, right?

Kind regards,
T.