New answers tagged

1

I've found where problem was! When I've created wrapper script, I've missed that it's in bash, and that through other tutorial, I've set the default shell to be /usr/lib/sftp-server. Afterwards, wrapper script started to work and I logged which commands I need to allow. Solution: 1.reverted shell (from /usr/lib/sftp-server), so wrapper could work: ...


1

ForceCommand is not filter, but forced command regardless the command-line as the name proposes. rsync requires to run different commands (as far as I know ... yes, sshd -ddd and ssh -vvv would be helpful to provide). One possibility is to leave the ChrootDirectory, remove ForceCommand and copy rsync, maybe some shell and it's dependencies (ldd ...


-1

One possible reason for this -- one that I hit -- was that I had no more free space on the disk I mounted.


0

I've seen the behavior you describe before, but testing it now I can create symlinks just fine on an sshfs-mounted directory: $ touch T $ ln -s T L $ ls -l T L lrwxrwxrwx 1 user user 1 Apr 9 16:10 L -> T -rw-rw-r-- 1 user user 0 Apr 9 16:10 T $ echo hello >> L $ cat T hello $ pwd /home/user/oak/tmp $ mount | grep oak user@oak: on /home/user/oak ...


0

Have you tried "killall sshfs"? That always works for me. Of course if you have more than one, you might want to narrow it down (ps -ef f) + (kill ###). You might need to kill[all] "-9" ###. I've found that certain unclean umounts leave the process running and tie up the sshfs system (or at least that directory) until the process is killed. (Sometimes, ...



Top 50 recent answers are included