Hello, all. We are finding that, as we add and delete shares to local media, the virtual desktop is becoming cluttered with artifacts from the file sharing. These appear to be sshfs disk definitions but they do not appear as devices (e.g., allowing mounts).
Ah, this is ringing a bell from when we worked with X2Go a year ago. Our tmp file system is in a separate tmpfs partition and set to noexec,nosuid,nodev. I would assume these artifacts are supposed to be devices but fail because they are located in /tmp and we are set to nodev.
Is there any way to create the devices some place else besides /tmp?
Hello John,
/tmp was choosen because in every other part of the directory structure ubuntu tries to mount the sshfs device itself.
best regards,
Heinz
On Fri, 2010-02-05 at 21:04 +0100, Heinz-M. Graesing wrote:
Hello, all. We are finding that, as we add and delete shares to local media, the virtual desktop is becoming cluttered with artifacts from the file sharing. These appear to be sshfs disk definitions but they do not appear as devices (e.g., allowing mounts).
Ah, this is ringing a bell from when we worked with X2Go a year ago. Our tmp file system is in a separate tmpfs partition and set to noexec,nosuid,nodev. I would assume these artifacts are supposed to be devices but fail because they are located in /tmp and we are set to nodev.
Is there any way to create the devices some place else besides /tmp?
Hello John,
/tmp was choosen because in every other part of the directory structure ubuntu tries to mount the sshfs device itself. <snip> No need to reply -- just reporting in our results especially since this is unsupported Hardy. We will be testing Lenny shortly.
Funnily, when I told the icons on my desktop to reorganize, the ugly artifacts turned into device icons but they were all mounted and they could not unmount. I reconfigured the VServer running X2Go so tmp was now exec,suid,dev. This changed nothing. The devices could neither mount nor unmount. The devices seem to be automounted when I shared them from the X2Go Client.
I also noticed that sshfs is a little more hit and miss than I'd like for production. When we start a fresh session, sometimes we can share local media and sometimes we cannot. We get errors such as:
sshd[9540]: error: channel_setup_fwd_listener: cannot listen to port: 30002
Again, no need to fret unless this persists on Lenny. Thanks - John
-
Heinz-M. Graesing -
John A. Sullivan III