В Fri, 12 Jul 2013 10:00:32 -0700
cac...@quantum-sci.com пишет:
Reindl Harald:
the example settings below mean i have 30 seconds
which my ssh-tunnels and connections are surviving
network downtime for whatever reason
Server (/etc/ssh/sshd_config):
TCPKeepAlive yes
KeepAlive yes
cac...@quantum-sci.com:
Dave Reisner:
On Thu, Jul 11, 2013 at 12:57:22PM -0700, cac...@quantum-sci.com wrote:
I'd understood that if a mount is in fstab, that it should be
re-established when the system wakes. But that's not happening.
Meaning two sshfs mounts as so:
sshfs#carl@droog:/
Your use of sshfs# as a FUSE type is wrong -- you must use fuse.sshfs as
the fstype instead.
this simply wrong, this line below in /etc/fstab works day
and night from FC9 to Fedora 18 as well as curlftpsfs
mounts in /etc/fstab are starting with curlftpfs#
and *both* have fuse and nothing else
On Fri, Jul 12, 2013 at 05:46:37PM +0200, Reindl Harald wrote:
Your use of sshfs# as a FUSE type is wrong -- you must use fuse.sshfs as
the fstype instead.
this simply wrong, this line below in /etc/fstab works day
and night from FC9 to Fedora 18 as well as curlftpsfs
mounts in
Am 12.07.2013 17:54, schrieb Dave Reisner:
On Fri, Jul 12, 2013 at 05:46:37PM +0200, Reindl Harald wrote:
Your use of sshfs# as a FUSE type is wrong -- you must use fuse.sshfs as
the fstype instead.
this simply wrong, this line below in /etc/fstab works day
and night from FC9 to Fedora 18
Reindl Harald:
Your use of sshfs# as a FUSE type is wrong -- you must use fuse.sshfs as
the fstype instead.
this simply wrong, this line below in /etc/fstab works day
and night from FC9 to Fedora 18 as well as curlftpsfs
mounts in /etc/fstab are starting with curlftpfs#
and *both* have fuse
Am 12.07.2013 17:58, schrieb cac...@quantum-sci.com:
Reindl Harald:
Your use of sshfs# as a FUSE type is wrong -- you must use fuse.sshfs as
the fstype instead.
this simply wrong, this line below in /etc/fstab works day
and night from FC9 to Fedora 18 as well as curlftpsfs
mounts in
On Fri, Jul 12, 2013 at 07:25:04AM -0700, cac...@quantum-sci.com wrote:
Lennart Poettering:
On Thu, 11.07.13 12:57, cac...@quantum-sci.com (cac...@quantum-sci.com)
wrote:
I'd understood that if a mount is in fstab, that it should be
re-established when the system wakes. But that's not
Dave Reisner:
On Fri, Jul 12, 2013 at 05:46:37PM +0200, Reindl Harald wrote:
Your use of sshfs# as a FUSE type is wrong -- you must use fuse.sshfs as
the fstype instead.
this simply wrong, this line below in /etc/fstab works day
and night from FC9 to Fedora 18 as well as curlftpsfs
mounts
2013/7/12 cac...@quantum-sci.com:
Reindl Harald:
Your use of sshfs# as a FUSE type is wrong -- you must use fuse.sshfs
as
the fstype instead.
this simply wrong, this line below in /etc/fstab works day
and night from FC9 to Fedora 18 as well as curlftpsfs
mounts in /etc/fstab are
Tomasz Torcz:
Second, the solution. The functionality you want is provide by ”automount”.
When using fstab, you can use the handy shortcut of putting
”x-systemd.automount” in your fstab. Best replace your ”auto” with
”x-systemd.automount”.
For details, see man systemd.mount.
Thank you.
I'd understood that if a mount is in fstab, that it should be
re-established when the system wakes. But that's not happening.
Meaning two sshfs mounts as so:
sshfs#carl@droog:/ /media/droog fuse
user,auto,_netdev,gid=6,umask=007,cache=no,ServerAliveInterval=15,allow_other,comment=sshfs
0 0
12 matches
Mail list logo
