Re: [systemd-devel] fstab Mounts Not Getting Waken Up

2013-07-12 Thread CACook
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:/

Re: [systemd-devel] fstab Mounts Not Getting Waken Up

2013-07-12 Thread CACook
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

Re: [systemd-devel] fstab Mounts Not Getting Waken Up

2013-07-12 Thread CACook
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

Re: [systemd-devel] fstab Mounts Not Getting Waken Up

2013-07-12 Thread CACook
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.

[systemd-devel] fstab Mounts Not Getting Waken Up

2013-07-11 Thread CACook
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

Re: [systemd-devel] Setting Up SSH Tunnels

2013-07-06 Thread CACook
Reindl, thanks again for your help yesterday. I have hassled for years with my unreliable method of setting up the SSH tunnels. Reindl Harald: with the small script below i see the status of all forwarding-services including all ssh processes with their params and the last restart-time

[systemd-devel] Setting Up SSH Tunnels

2013-07-05 Thread CACook
For some years I've set up reverse SSH tunnels with a script, but when the tunnels go down they do not recover. I'd like to start and stop the tunnels using systemd. A typical command looks like this: /usr/bin/ssh -f -l sleeper -i /home/sleeper/.ssh/id_ecdsa -2 -4 -c aes256-ctr,aes128-ctr

Re: [systemd-devel] Setting Up SSH Tunnels

2013-07-05 Thread CACook
Reindl Harald: But does this mean I have to have over 20 .services for my reverse tunnels? They could all start in parallel, but is there no better way? this is a *perfect* way and the only one Restart=always can work relieable no matter how many of them, build one, test it carefully and copy

Re: [systemd-devel] Setting Up SSH Tunnels

2013-07-05 Thread CACook
Reindl Harald: Am 05.07.2013 23:03, schrieb cac...@quantum-sci.com: Yes your command works standalone, and mine does too. The difference is yours does not release the shell. Maybe this is necessary for process tracking? if you think about how Restart=always works clearly *yes* But