I am not seeing "Transport endpoint not connected" (since it is
connected), but:
execute as root:
--- snip ----
u...@maverick:~$ sshfs -o nonempty,cache=yes,noatime,allow_other,\
uid=2023,gid=2023 -p 10046 u...@remote-host: /remote/user
u...@remote-host's password:
u...@maverick:~$ ls -la /remote
total 12
drwxr-xr-x 3 root root 4096 2010-12-30 13:13 .
drwxr-xr-x 24 root root 4096 2010-12-30 13:09 ..
drwxr-x--- 1 user user 4096 2010-12-15 10:39 user
u...@maverick:~$ cd /remote/user/
u...@maverick:/remote/user $ ls -la
total 252
drwxr-x--- 1 user user 4096 2010-12-15 10:39 .
drwxr-xr-x 3 root root 4096 2010-12-30 13:13 ..
drwx------ 1 user user 4096 2010-12-09 13:01 .aptitude
-rw------- 1 user user 6488 2010-12-30 13:23 .bash_history
-rw-r--r-- 1 user user 122 2010-10-05 17:42 .bashrc
drwxr-xr-x 1 user user 4096 2010-11-24 12:56 bin
--- snap ----
It is possible to access the files on the remote, sshfs mounted server.
Now the same, this time mounted by root:
--- snip ----
r...@maverick:~# sshfs -o nonempty,cache=yes,noatime,allow_other,\
uid=2023,gid=2023 -p 10046 u...@remote-host: /remote/user
[email protected]'s password:
r...@maverick:~# ls -la /remote
total 12
drwxr-xr-x 3 root root 4096 2010-12-30 13:13 .
drwxr-xr-x 24 root root 4096 2010-12-30 13:09 ..
drwxr-x--- 1 user user 4096 2010-12-15 10:39 user
r...@maverick:~# su - user
u...@maverick:~$ ls -ls /home/
total 20
d????????? ? ? ? 0 ? user
--- snap ----
The directory is not accessible by the user. Quite annoying if the mount
is done by autofs!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/604142
Title:
Transport endpoint is not connected
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
