On 18 November 2015 at 13:23, Lennart Poettering wrote:
> The problem is with actually invoking processes such as the fuse.sshfs
> one as a non-root user.
But in my case there are no non-root processes! uid/gid options is
used just for *ownership of files and directories* under the mount
point, t
On Wed, 18.11.15 13:02, Igor Bukanov ([email protected]) wrote:
> On 18 November 2015 at 12:28, Lennart Poettering
> wrote:
> > We don't support that. Invoking user processes from a system context
> > is something we generally avoid.
>
> Could you clarify how this is related to an ability to invoke
On 18 November 2015 at 12:28, Lennart Poettering wrote:
> We don't support that. Invoking user processes from a system context
> is something we generally avoid.
Could you clarify how this is related to an ability to invoke a user
process? For example, I can explicitly pass uid=1000,gid=1000 as a
On Wed, 18.11.15 11:58, Igor Bukanov ([email protected]) wrote:
> Hello,
>
> I am trying to translate an autofs map into systemd unit files, but I
> could not see how to pass to the mount command an option refering to
> the user who accessed the mount dir. For example, the automap
> contains:
>
> /m
Hello,
I am trying to translate an autofs map into systemd unit files, but I
could not see how to pass to the mount command an option refering to
the user who accessed the mount dir. For example, the automap
contains:
/mount/dir -fstype=fuse.sshfs,...,id=$UID,gid=$GID remote_user@host:/dir
which
