sshfs with on-demand mounting
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I followed instructions for sshfs "on demand" mounting, but it doesn't work.
I added this to /etc/fstab
:
username@hostname:/ /mnt/remotes/hostname fuse.sshfs noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home/stanley/.ssh/my_rsa_key,allow_other,reconnect 0 0
Then I ran sudo mount -a
which did nothing. I also tried systemctl daemon-reload && systemctl restart proc-sys-fs-binfmt_misc.automount
.
So I followed the troubleshooting tips, and used this instead:
username@hostname:/ /mnt/remotes/hostname fuse.sshfs ssh_command=ssh40-vv,sshfs_debug,debug,_netdev,users,idmap=user,IdentityFile=/home/stanley/.ssh/my_rsa_key,allow_other,reconnect 0 0
And then ran sudo mount -av
. In a separate terminal I could access that mount point.
So 1) ssh and sftp are working, 2) sshfs is working, 3) permissions are fine.
So only the on-demand part isn't working - what am I doing wrong?
ubuntu ssh fstab sftp sshfs
add a comment |Â
up vote
0
down vote
favorite
I followed instructions for sshfs "on demand" mounting, but it doesn't work.
I added this to /etc/fstab
:
username@hostname:/ /mnt/remotes/hostname fuse.sshfs noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home/stanley/.ssh/my_rsa_key,allow_other,reconnect 0 0
Then I ran sudo mount -a
which did nothing. I also tried systemctl daemon-reload && systemctl restart proc-sys-fs-binfmt_misc.automount
.
So I followed the troubleshooting tips, and used this instead:
username@hostname:/ /mnt/remotes/hostname fuse.sshfs ssh_command=ssh40-vv,sshfs_debug,debug,_netdev,users,idmap=user,IdentityFile=/home/stanley/.ssh/my_rsa_key,allow_other,reconnect 0 0
And then ran sudo mount -av
. In a separate terminal I could access that mount point.
So 1) ssh and sftp are working, 2) sshfs is working, 3) permissions are fine.
So only the on-demand part isn't working - what am I doing wrong?
ubuntu ssh fstab sftp sshfs
By the way, I know aboutautofs
, but I don't want to use it because it only works for root.
â lonix
Sep 5 at 16:59
it is preferred to use the "edit" link underneath the answer to update it, rather than adding separate comments.
â sourcejedi
Sep 5 at 17:53
The comment has nothing to do with the question, I'm expecting an answer of the "why don't you rather use tool XYZ", so I tried to avoid it :)
â lonix
Sep 5 at 18:29
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I followed instructions for sshfs "on demand" mounting, but it doesn't work.
I added this to /etc/fstab
:
username@hostname:/ /mnt/remotes/hostname fuse.sshfs noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home/stanley/.ssh/my_rsa_key,allow_other,reconnect 0 0
Then I ran sudo mount -a
which did nothing. I also tried systemctl daemon-reload && systemctl restart proc-sys-fs-binfmt_misc.automount
.
So I followed the troubleshooting tips, and used this instead:
username@hostname:/ /mnt/remotes/hostname fuse.sshfs ssh_command=ssh40-vv,sshfs_debug,debug,_netdev,users,idmap=user,IdentityFile=/home/stanley/.ssh/my_rsa_key,allow_other,reconnect 0 0
And then ran sudo mount -av
. In a separate terminal I could access that mount point.
So 1) ssh and sftp are working, 2) sshfs is working, 3) permissions are fine.
So only the on-demand part isn't working - what am I doing wrong?
ubuntu ssh fstab sftp sshfs
I followed instructions for sshfs "on demand" mounting, but it doesn't work.
I added this to /etc/fstab
:
username@hostname:/ /mnt/remotes/hostname fuse.sshfs noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home/stanley/.ssh/my_rsa_key,allow_other,reconnect 0 0
Then I ran sudo mount -a
which did nothing. I also tried systemctl daemon-reload && systemctl restart proc-sys-fs-binfmt_misc.automount
.
So I followed the troubleshooting tips, and used this instead:
username@hostname:/ /mnt/remotes/hostname fuse.sshfs ssh_command=ssh40-vv,sshfs_debug,debug,_netdev,users,idmap=user,IdentityFile=/home/stanley/.ssh/my_rsa_key,allow_other,reconnect 0 0
And then ran sudo mount -av
. In a separate terminal I could access that mount point.
So 1) ssh and sftp are working, 2) sshfs is working, 3) permissions are fine.
So only the on-demand part isn't working - what am I doing wrong?
ubuntu ssh fstab sftp sshfs
ubuntu ssh fstab sftp sshfs
edited Sep 5 at 18:30
asked Sep 5 at 16:59
lonix
31719
31719
By the way, I know aboutautofs
, but I don't want to use it because it only works for root.
â lonix
Sep 5 at 16:59
it is preferred to use the "edit" link underneath the answer to update it, rather than adding separate comments.
â sourcejedi
Sep 5 at 17:53
The comment has nothing to do with the question, I'm expecting an answer of the "why don't you rather use tool XYZ", so I tried to avoid it :)
â lonix
Sep 5 at 18:29
add a comment |Â
By the way, I know aboutautofs
, but I don't want to use it because it only works for root.
â lonix
Sep 5 at 16:59
it is preferred to use the "edit" link underneath the answer to update it, rather than adding separate comments.
â sourcejedi
Sep 5 at 17:53
The comment has nothing to do with the question, I'm expecting an answer of the "why don't you rather use tool XYZ", so I tried to avoid it :)
â lonix
Sep 5 at 18:29
By the way, I know about
autofs
, but I don't want to use it because it only works for root.â lonix
Sep 5 at 16:59
By the way, I know about
autofs
, but I don't want to use it because it only works for root.â lonix
Sep 5 at 16:59
it is preferred to use the "edit" link underneath the answer to update it, rather than adding separate comments.
â sourcejedi
Sep 5 at 17:53
it is preferred to use the "edit" link underneath the answer to update it, rather than adding separate comments.
â sourcejedi
Sep 5 at 17:53
The comment has nothing to do with the question, I'm expecting an answer of the "why don't you rather use tool XYZ", so I tried to avoid it :)
â lonix
Sep 5 at 18:29
The comment has nothing to do with the question, I'm expecting an answer of the "why don't you rather use tool XYZ", so I tried to avoid it :)
â lonix
Sep 5 at 18:29
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
The instructions say:
Note: After editing /etc/fstab, (re)start the required service: systemctl daemon-reload && systemctl restart where
<target>
can be found by running systemctl list-unit-files --type automount
You have a problem :-(.
Mount options which are implemented by systemd, such as x-systemd.*
, are not implemented by the mount
command.
But the mount
command is what you need to use, if you are an unprivileged user (no root/sudo), and you want to mount an fstab entry (which has been marked to allow this using the user
or users
mount option).
I should have mentioned, I did that too - didn't help -systemctl daemon-reload && systemctl restart proc-sys-fs-binfmt_misc.automount
â lonix
Sep 5 at 18:27
Okay the order I issued the commands in was wrong (the instructions are confusing) and so I used the wrong unit file. I added a step by step answer to help anyone else. But you led me the right direction so thank you.
â lonix
Sep 6 at 6:03
One more thing: to unmount, is it correct to useunmount mountpoint
or to usesudo systemctl stop mnt-remotes-hostname.automount
? You mentioned systemd doesn't work withmount
, so do I assume the same forumount
? (both ways work, so I'm unsure which is safer/correct)
â lonix
Sep 6 at 7:07
1
But I'm a bit worried aboutsystemctl stop whatever.automount
if you haven't already stopped the mount unit, after reading github.com/systemd/systemd/issues/6754
â sourcejedi
Sep 6 at 7:51
1
Ok so I'll always dosystemctl stop whatever.mount && systemctl stop whatever.automount
to be on the safe side, and never useumount
. Thanks for the warning.
â lonix
Sep 6 at 8:16
 |Â
show 1 more comment
up vote
1
down vote
The instructions are confusing, especially for someone who doesn't understand systemd.
The correct procedure:
add to
/etc/fstab
:username@hostname:/ /mnt/remotes/hostname fuse.sshfs noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home/stanley/.ssh/my_rsa_key,allow_other,reconnect 0 0
run
sudo systemctl daemon-reload
. This creates a systemd "unit file".find out which unit file by running
systemctl list-unit-files --type automount
. For me it wasmnt-remotes-hostname.automount
.enable it:
sudo systemctl restart mnt-remotes-hostname.automount
.cd /mnt/remotes/hostname
orls /mnt/remotes/hostname
and it will automatically create the sftp connection!
That works, but I'm not yet sure about:
- some say
allow_other
is a security risk, I'll need to look into that - I don't know how to specify when the mount should be automatically unmounted (how many seconds of idle time, etc.)
If anyone can shed light on that, please do.
UPDATE
As per @sourcejedis's answer, stopping the mount must be done in this order: systemctl stop whatever.mount && systemctl stop whatever.automount
and one should NOT use umount mounpoint
!
1
allow_other
should not allow privilege escalation, only denial of service (cause process to hang, it can be killed though). I wouldn't enable it if you don't want the feature it provides, but if you do then I would just do it :-).
â sourcejedi
Sep 5 at 20:43
1
x-systemd.idle-timeout=
as perman systemd.mount
â sourcejedi
Sep 5 at 20:44
@sourcejedi Thanks for those missing pieces of the puzzle!
â lonix
Sep 6 at 5:56
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
The instructions say:
Note: After editing /etc/fstab, (re)start the required service: systemctl daemon-reload && systemctl restart where
<target>
can be found by running systemctl list-unit-files --type automount
You have a problem :-(.
Mount options which are implemented by systemd, such as x-systemd.*
, are not implemented by the mount
command.
But the mount
command is what you need to use, if you are an unprivileged user (no root/sudo), and you want to mount an fstab entry (which has been marked to allow this using the user
or users
mount option).
I should have mentioned, I did that too - didn't help -systemctl daemon-reload && systemctl restart proc-sys-fs-binfmt_misc.automount
â lonix
Sep 5 at 18:27
Okay the order I issued the commands in was wrong (the instructions are confusing) and so I used the wrong unit file. I added a step by step answer to help anyone else. But you led me the right direction so thank you.
â lonix
Sep 6 at 6:03
One more thing: to unmount, is it correct to useunmount mountpoint
or to usesudo systemctl stop mnt-remotes-hostname.automount
? You mentioned systemd doesn't work withmount
, so do I assume the same forumount
? (both ways work, so I'm unsure which is safer/correct)
â lonix
Sep 6 at 7:07
1
But I'm a bit worried aboutsystemctl stop whatever.automount
if you haven't already stopped the mount unit, after reading github.com/systemd/systemd/issues/6754
â sourcejedi
Sep 6 at 7:51
1
Ok so I'll always dosystemctl stop whatever.mount && systemctl stop whatever.automount
to be on the safe side, and never useumount
. Thanks for the warning.
â lonix
Sep 6 at 8:16
 |Â
show 1 more comment
up vote
1
down vote
accepted
The instructions say:
Note: After editing /etc/fstab, (re)start the required service: systemctl daemon-reload && systemctl restart where
<target>
can be found by running systemctl list-unit-files --type automount
You have a problem :-(.
Mount options which are implemented by systemd, such as x-systemd.*
, are not implemented by the mount
command.
But the mount
command is what you need to use, if you are an unprivileged user (no root/sudo), and you want to mount an fstab entry (which has been marked to allow this using the user
or users
mount option).
I should have mentioned, I did that too - didn't help -systemctl daemon-reload && systemctl restart proc-sys-fs-binfmt_misc.automount
â lonix
Sep 5 at 18:27
Okay the order I issued the commands in was wrong (the instructions are confusing) and so I used the wrong unit file. I added a step by step answer to help anyone else. But you led me the right direction so thank you.
â lonix
Sep 6 at 6:03
One more thing: to unmount, is it correct to useunmount mountpoint
or to usesudo systemctl stop mnt-remotes-hostname.automount
? You mentioned systemd doesn't work withmount
, so do I assume the same forumount
? (both ways work, so I'm unsure which is safer/correct)
â lonix
Sep 6 at 7:07
1
But I'm a bit worried aboutsystemctl stop whatever.automount
if you haven't already stopped the mount unit, after reading github.com/systemd/systemd/issues/6754
â sourcejedi
Sep 6 at 7:51
1
Ok so I'll always dosystemctl stop whatever.mount && systemctl stop whatever.automount
to be on the safe side, and never useumount
. Thanks for the warning.
â lonix
Sep 6 at 8:16
 |Â
show 1 more comment
up vote
1
down vote
accepted
up vote
1
down vote
accepted
The instructions say:
Note: After editing /etc/fstab, (re)start the required service: systemctl daemon-reload && systemctl restart where
<target>
can be found by running systemctl list-unit-files --type automount
You have a problem :-(.
Mount options which are implemented by systemd, such as x-systemd.*
, are not implemented by the mount
command.
But the mount
command is what you need to use, if you are an unprivileged user (no root/sudo), and you want to mount an fstab entry (which has been marked to allow this using the user
or users
mount option).
The instructions say:
Note: After editing /etc/fstab, (re)start the required service: systemctl daemon-reload && systemctl restart where
<target>
can be found by running systemctl list-unit-files --type automount
You have a problem :-(.
Mount options which are implemented by systemd, such as x-systemd.*
, are not implemented by the mount
command.
But the mount
command is what you need to use, if you are an unprivileged user (no root/sudo), and you want to mount an fstab entry (which has been marked to allow this using the user
or users
mount option).
edited Sep 5 at 20:55
answered Sep 5 at 17:56
sourcejedi
20.3k42887
20.3k42887
I should have mentioned, I did that too - didn't help -systemctl daemon-reload && systemctl restart proc-sys-fs-binfmt_misc.automount
â lonix
Sep 5 at 18:27
Okay the order I issued the commands in was wrong (the instructions are confusing) and so I used the wrong unit file. I added a step by step answer to help anyone else. But you led me the right direction so thank you.
â lonix
Sep 6 at 6:03
One more thing: to unmount, is it correct to useunmount mountpoint
or to usesudo systemctl stop mnt-remotes-hostname.automount
? You mentioned systemd doesn't work withmount
, so do I assume the same forumount
? (both ways work, so I'm unsure which is safer/correct)
â lonix
Sep 6 at 7:07
1
But I'm a bit worried aboutsystemctl stop whatever.automount
if you haven't already stopped the mount unit, after reading github.com/systemd/systemd/issues/6754
â sourcejedi
Sep 6 at 7:51
1
Ok so I'll always dosystemctl stop whatever.mount && systemctl stop whatever.automount
to be on the safe side, and never useumount
. Thanks for the warning.
â lonix
Sep 6 at 8:16
 |Â
show 1 more comment
I should have mentioned, I did that too - didn't help -systemctl daemon-reload && systemctl restart proc-sys-fs-binfmt_misc.automount
â lonix
Sep 5 at 18:27
Okay the order I issued the commands in was wrong (the instructions are confusing) and so I used the wrong unit file. I added a step by step answer to help anyone else. But you led me the right direction so thank you.
â lonix
Sep 6 at 6:03
One more thing: to unmount, is it correct to useunmount mountpoint
or to usesudo systemctl stop mnt-remotes-hostname.automount
? You mentioned systemd doesn't work withmount
, so do I assume the same forumount
? (both ways work, so I'm unsure which is safer/correct)
â lonix
Sep 6 at 7:07
1
But I'm a bit worried aboutsystemctl stop whatever.automount
if you haven't already stopped the mount unit, after reading github.com/systemd/systemd/issues/6754
â sourcejedi
Sep 6 at 7:51
1
Ok so I'll always dosystemctl stop whatever.mount && systemctl stop whatever.automount
to be on the safe side, and never useumount
. Thanks for the warning.
â lonix
Sep 6 at 8:16
I should have mentioned, I did that too - didn't help -
systemctl daemon-reload && systemctl restart proc-sys-fs-binfmt_misc.automount
â lonix
Sep 5 at 18:27
I should have mentioned, I did that too - didn't help -
systemctl daemon-reload && systemctl restart proc-sys-fs-binfmt_misc.automount
â lonix
Sep 5 at 18:27
Okay the order I issued the commands in was wrong (the instructions are confusing) and so I used the wrong unit file. I added a step by step answer to help anyone else. But you led me the right direction so thank you.
â lonix
Sep 6 at 6:03
Okay the order I issued the commands in was wrong (the instructions are confusing) and so I used the wrong unit file. I added a step by step answer to help anyone else. But you led me the right direction so thank you.
â lonix
Sep 6 at 6:03
One more thing: to unmount, is it correct to use
unmount mountpoint
or to use sudo systemctl stop mnt-remotes-hostname.automount
? You mentioned systemd doesn't work with mount
, so do I assume the same for umount
? (both ways work, so I'm unsure which is safer/correct)â lonix
Sep 6 at 7:07
One more thing: to unmount, is it correct to use
unmount mountpoint
or to use sudo systemctl stop mnt-remotes-hostname.automount
? You mentioned systemd doesn't work with mount
, so do I assume the same for umount
? (both ways work, so I'm unsure which is safer/correct)â lonix
Sep 6 at 7:07
1
1
But I'm a bit worried about
systemctl stop whatever.automount
if you haven't already stopped the mount unit, after reading github.com/systemd/systemd/issues/6754â sourcejedi
Sep 6 at 7:51
But I'm a bit worried about
systemctl stop whatever.automount
if you haven't already stopped the mount unit, after reading github.com/systemd/systemd/issues/6754â sourcejedi
Sep 6 at 7:51
1
1
Ok so I'll always do
systemctl stop whatever.mount && systemctl stop whatever.automount
to be on the safe side, and never use umount
. Thanks for the warning.â lonix
Sep 6 at 8:16
Ok so I'll always do
systemctl stop whatever.mount && systemctl stop whatever.automount
to be on the safe side, and never use umount
. Thanks for the warning.â lonix
Sep 6 at 8:16
 |Â
show 1 more comment
up vote
1
down vote
The instructions are confusing, especially for someone who doesn't understand systemd.
The correct procedure:
add to
/etc/fstab
:username@hostname:/ /mnt/remotes/hostname fuse.sshfs noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home/stanley/.ssh/my_rsa_key,allow_other,reconnect 0 0
run
sudo systemctl daemon-reload
. This creates a systemd "unit file".find out which unit file by running
systemctl list-unit-files --type automount
. For me it wasmnt-remotes-hostname.automount
.enable it:
sudo systemctl restart mnt-remotes-hostname.automount
.cd /mnt/remotes/hostname
orls /mnt/remotes/hostname
and it will automatically create the sftp connection!
That works, but I'm not yet sure about:
- some say
allow_other
is a security risk, I'll need to look into that - I don't know how to specify when the mount should be automatically unmounted (how many seconds of idle time, etc.)
If anyone can shed light on that, please do.
UPDATE
As per @sourcejedis's answer, stopping the mount must be done in this order: systemctl stop whatever.mount && systemctl stop whatever.automount
and one should NOT use umount mounpoint
!
1
allow_other
should not allow privilege escalation, only denial of service (cause process to hang, it can be killed though). I wouldn't enable it if you don't want the feature it provides, but if you do then I would just do it :-).
â sourcejedi
Sep 5 at 20:43
1
x-systemd.idle-timeout=
as perman systemd.mount
â sourcejedi
Sep 5 at 20:44
@sourcejedi Thanks for those missing pieces of the puzzle!
â lonix
Sep 6 at 5:56
add a comment |Â
up vote
1
down vote
The instructions are confusing, especially for someone who doesn't understand systemd.
The correct procedure:
add to
/etc/fstab
:username@hostname:/ /mnt/remotes/hostname fuse.sshfs noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home/stanley/.ssh/my_rsa_key,allow_other,reconnect 0 0
run
sudo systemctl daemon-reload
. This creates a systemd "unit file".find out which unit file by running
systemctl list-unit-files --type automount
. For me it wasmnt-remotes-hostname.automount
.enable it:
sudo systemctl restart mnt-remotes-hostname.automount
.cd /mnt/remotes/hostname
orls /mnt/remotes/hostname
and it will automatically create the sftp connection!
That works, but I'm not yet sure about:
- some say
allow_other
is a security risk, I'll need to look into that - I don't know how to specify when the mount should be automatically unmounted (how many seconds of idle time, etc.)
If anyone can shed light on that, please do.
UPDATE
As per @sourcejedis's answer, stopping the mount must be done in this order: systemctl stop whatever.mount && systemctl stop whatever.automount
and one should NOT use umount mounpoint
!
1
allow_other
should not allow privilege escalation, only denial of service (cause process to hang, it can be killed though). I wouldn't enable it if you don't want the feature it provides, but if you do then I would just do it :-).
â sourcejedi
Sep 5 at 20:43
1
x-systemd.idle-timeout=
as perman systemd.mount
â sourcejedi
Sep 5 at 20:44
@sourcejedi Thanks for those missing pieces of the puzzle!
â lonix
Sep 6 at 5:56
add a comment |Â
up vote
1
down vote
up vote
1
down vote
The instructions are confusing, especially for someone who doesn't understand systemd.
The correct procedure:
add to
/etc/fstab
:username@hostname:/ /mnt/remotes/hostname fuse.sshfs noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home/stanley/.ssh/my_rsa_key,allow_other,reconnect 0 0
run
sudo systemctl daemon-reload
. This creates a systemd "unit file".find out which unit file by running
systemctl list-unit-files --type automount
. For me it wasmnt-remotes-hostname.automount
.enable it:
sudo systemctl restart mnt-remotes-hostname.automount
.cd /mnt/remotes/hostname
orls /mnt/remotes/hostname
and it will automatically create the sftp connection!
That works, but I'm not yet sure about:
- some say
allow_other
is a security risk, I'll need to look into that - I don't know how to specify when the mount should be automatically unmounted (how many seconds of idle time, etc.)
If anyone can shed light on that, please do.
UPDATE
As per @sourcejedis's answer, stopping the mount must be done in this order: systemctl stop whatever.mount && systemctl stop whatever.automount
and one should NOT use umount mounpoint
!
The instructions are confusing, especially for someone who doesn't understand systemd.
The correct procedure:
add to
/etc/fstab
:username@hostname:/ /mnt/remotes/hostname fuse.sshfs noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home/stanley/.ssh/my_rsa_key,allow_other,reconnect 0 0
run
sudo systemctl daemon-reload
. This creates a systemd "unit file".find out which unit file by running
systemctl list-unit-files --type automount
. For me it wasmnt-remotes-hostname.automount
.enable it:
sudo systemctl restart mnt-remotes-hostname.automount
.cd /mnt/remotes/hostname
orls /mnt/remotes/hostname
and it will automatically create the sftp connection!
That works, but I'm not yet sure about:
- some say
allow_other
is a security risk, I'll need to look into that - I don't know how to specify when the mount should be automatically unmounted (how many seconds of idle time, etc.)
If anyone can shed light on that, please do.
UPDATE
As per @sourcejedis's answer, stopping the mount must be done in this order: systemctl stop whatever.mount && systemctl stop whatever.automount
and one should NOT use umount mounpoint
!
edited Sep 6 at 8:18
answered Sep 5 at 19:25
lonix
31719
31719
1
allow_other
should not allow privilege escalation, only denial of service (cause process to hang, it can be killed though). I wouldn't enable it if you don't want the feature it provides, but if you do then I would just do it :-).
â sourcejedi
Sep 5 at 20:43
1
x-systemd.idle-timeout=
as perman systemd.mount
â sourcejedi
Sep 5 at 20:44
@sourcejedi Thanks for those missing pieces of the puzzle!
â lonix
Sep 6 at 5:56
add a comment |Â
1
allow_other
should not allow privilege escalation, only denial of service (cause process to hang, it can be killed though). I wouldn't enable it if you don't want the feature it provides, but if you do then I would just do it :-).
â sourcejedi
Sep 5 at 20:43
1
x-systemd.idle-timeout=
as perman systemd.mount
â sourcejedi
Sep 5 at 20:44
@sourcejedi Thanks for those missing pieces of the puzzle!
â lonix
Sep 6 at 5:56
1
1
allow_other
should not allow privilege escalation, only denial of service (cause process to hang, it can be killed though). I wouldn't enable it if you don't want the feature it provides, but if you do then I would just do it :-).â sourcejedi
Sep 5 at 20:43
allow_other
should not allow privilege escalation, only denial of service (cause process to hang, it can be killed though). I wouldn't enable it if you don't want the feature it provides, but if you do then I would just do it :-).â sourcejedi
Sep 5 at 20:43
1
1
x-systemd.idle-timeout=
as per man systemd.mount
â sourcejedi
Sep 5 at 20:44
x-systemd.idle-timeout=
as per man systemd.mount
â sourcejedi
Sep 5 at 20:44
@sourcejedi Thanks for those missing pieces of the puzzle!
â lonix
Sep 6 at 5:56
@sourcejedi Thanks for those missing pieces of the puzzle!
â lonix
Sep 6 at 5:56
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f467081%2fsshfs-with-on-demand-mounting%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
By the way, I know about
autofs
, but I don't want to use it because it only works for root.â lonix
Sep 5 at 16:59
it is preferred to use the "edit" link underneath the answer to update it, rather than adding separate comments.
â sourcejedi
Sep 5 at 17:53
The comment has nothing to do with the question, I'm expecting an answer of the "why don't you rather use tool XYZ", so I tried to avoid it :)
â lonix
Sep 5 at 18:29