Oops! My apologies. I was confusing it with x2goumount_session. I believe the mount logic is in x2gomountdirs - John
On Tue, 2010-06-22 at 19:37 -0500, Gerry Reno wrote: > Ok, here is 'mount' on the server: > # mount > /dev/sda1 on / type ext3 (rw) > proc on /proc type proc (rw,noexec,nosuid,nodev) > none on /sys type sysfs (rw,noexec,nosuid,nodev) > none on /sys/kernel/debug type debugfs (rw) > none on /sys/kernel/security type securityfs (rw) > devtmpfs on /dev type devtmpfs (rw,mode=0755) > none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) > none on /dev/shm type tmpfs (rw,nosuid,nodev) > none on /var/run type tmpfs (rw,nosuid,mode=0755) > none on /var/lock type tmpfs (rw,noexec,nosuid,nodev) > none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) > /dev/sdb on /mnt type ext3 (rw) > > I don't see any sshfs shares. > > # ls -l /usr/bin/x2gomount_sessions > ls: cannot access /usr/bin/x2gomount_sessions: No such file or > directory > # ls /usr/bin/x2go* > /usr/bin/x2goagent /usr/bin/x2gopgwrapper > /usr/bin/x2gostartagent > /usr/bin/x2goclient_gtk /usr/bin/x2gopgwrapper_local > /usr/bin/x2gosuspend-agent > /usr/bin/x2gocmdexitmessage /usr/bin/x2gopgwrapper_net > /usr/bin/x2gosuspend-session > /usr/bin/x2gogetservers /usr/bin/x2gopgwrapper_sqlite > /usr/bin/x2gosuspend-session-gnome > /usr/bin/x2golistsessions /usr/bin/x2goprint > /usr/bin/x2goterminate > /usr/bin/x2golistsessions_root /usr/bin/x2goresume-session > /usr/bin/x2goterminate-session > /usr/bin/x2golistsessions_sql /usr/bin/x2goruncommand > /usr/bin/x2goumount > /usr/bin/x2gomountdirs /usr/bin/x2gosessionlimit > /usr/bin/x2goumount_session > /usr/bin/x2gonautilus /usr/bin/x2goshowblocks > > No /usr/bin/x2gomount_sessions script. > > Would it be somewhere else? > > -Gerry > > > > > > Jun 22, 2010 08:27:54 PM, [email protected] wrote: > Yes. If you issue a mount command on the X2Go Server, do you > see the > mounts for the sshfs shares, e.g., > > j...@jas:~$ mount > /dev/hdv1 on / type ufs (defaults) > none on /proc type proc (defaults) > none on /tmp type tmpfs > (size=128m,mode=1777,noexec,nosuid,nodev) > none on /dev/pts type devpts (gid=5,mode=620) > > [email protected]:/home/jsull/.x2go/S-jas-54-1277203660_stDKDE_dp24/spool on > /tmp/spool_jas/jas-54-1277203660_stDKDE_dp24 type fuse.sshfs > (rw,nosuid,nodev,max_read=65536,user=jas) > [email protected]:/home/jsull/ on /tmp/jas_media/_home_jsull_ > type fuse.sshfs (rw,nosuid,nodev,max_read=65536,user=jas) > > If not, you might be able to add debugging information to > the /usr/bin/x2gomount_sessions script. > > If the mounts are there and it is still not working, you may > be able to > add debugging information to the cups-x2go backend as it is > simply a > perl script. I'm not sure where that is - > perhaps /usr/lib/cups/backends. Hope that helps - John > > On Tue, 2010-06-22 at 16:13 -0500, Gerry Reno wrote: > > Ok, tried adding my local user account to the fuse group so > it looks > > like this now: > > fuse:x:104:greno > > > > But, still no printing and no errors that I can find. Is > there some > > type of manual tests that can be run to check things out? > > > > -Gerry > > > > > > > > Jun 22, 2010 04:16:26 PM, [email protected] wrote: > > I'm not sure if it is still a requirement that the users be > > members of > > the fuse group on the client. We are set up that way by > force > > of habit. > > We also added the users to the various pulse groups - John > > > > On Tue, 2010-06-22 at 12:47 -0500, Gerry Reno wrote: > > > Hi John, > > > Thanks for the reply. I checked on sshfs, sshd and fuse. > > Here's > > > what I found: > > > > > > Server: > > > # apt-show-versions sshfs > > > sshfs/lucid uptodate 2.2-1build1 > > > # service ssh status > > > ssh start/running, process 409 > > > # modprobe -l | grep fuse > > > kernel/fs/fuse/fuse.ko > > > # cat /etc/group | grep -E 'fuse|x2go' > > > fuse:x:104:ubuntu > > > x2gousers:x:123:ubuntu > > > x2goprint:x:999:ubuntu > > > > > > Client: > > > # apt-show-versions sshfs > > > sshfs/lucid uptodate 2.2-1build1 > > > # service ssh status > > > ssh start/running, process 2191 > > > # modprobe -l | grep fuse > > > kernel/fs/fuse/cuse.ko > > > # cat /etc/group | grep -E 'fuse|x2go' > > > fuse:x:104: > > > x2gousers:x:131:greno > > > > > > > > > I don't see anything out of order there. Anything else you > > think I > > > can check? > > > > > > -Gerry > > > > > > Jun 22, 2010 07:53:06 AM, [email protected] wrote: > > > On Mon, 2010-06-21 at 20:41 -0500, Gerry Reno wrote: > > > > I have a lucid client and a lucid server. I followed the > > > guides for > > > > Linux and I can access the server from the client using > > x2go > > > and the > > > > session works fine. I cannot seem to get folder sharing > or > > > printing > > > > to work however. I have cups-x2go and x2goprint > installed > > on > > > the > > > > server. I've selected the proper options in the x2go > > client > > > interface > > > > (I shared one directory automounted) and for printing I > > > checked to > > > > print to xpdf. I verified that 'xpdf' is installed on > the > > > client. I > > > > have gone to Administration, Printing and set up the > > printer > > > > Generic-CUPS-X2GO-printer. I'm using ssh port 22 for > > > connections. > > > > When I print something from the remote desktop it acts > > likes > > > > everything worked. When I check > > the /var/log/cups/access_log > > > I can > > > > see everything seemed to work. But, no output ever > appears > > > anywhere. > > > > Also, with the shared folder, no folder is ever mounted > > > anywhere. Can > > > > someone shed some light on what is needed to get these > > > functions > > > > working? > > > > > > The fact that both are broken helps narrow it down. Both > use > > > fuse and > > > an sshfs mount to pass data. Do you have fuse and sshfs > > > installed? Is > > > sshd running on BOTH client and server? Are the users > > members > > > of the > > > fuse group to have access to the fuse device? Those are > the > > > areas I'd > > > suggest checking. Good luck - John > > > > > > _______________________________________________ > > > X2go-dev mailing list > > > [email protected] > > > https://lists.berlios.de/mailman/listinfo/x2go-dev > > > _______________________________________________ > > > X2go-dev mailing list > > > [email protected] > > > https://lists.berlios.de/mailman/listinfo/x2go-dev > > > > > > _______________________________________________ > > X2go-dev mailing list > > [email protected] > > https://lists.berlios.de/mailman/listinfo/x2go-dev > > _______________________________________________ > > X2go-dev mailing list > > [email protected] > > https://lists.berlios.de/mailman/listinfo/x2go-dev > > > _______________________________________________ > X2go-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/x2go-dev > _______________________________________________ > X2go-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/x2go-dev _______________________________________________ X2go-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/x2go-dev
