On Tue, 30 Oct 2007, Alexandre Magaz Graça wrote:
> Step 3: Did the ltsp udev rules fire?
>
> Yes, but I suppose the path to the fstab should be updated on the wiki.
>
> [EMAIL PROTECTED]:~# cat /var/run/ltspfs_fstab
> /dev/fd0 /var/run/drives/floppy0 auto defaults 0 0
> /dev/sdb1 /var/run/drives/usbdisk-sdb1 vfat defaults 0 0
>
> Step 4: Can you manually issue a mount command?
>
> I didn't found /tmp/.ltspfs_socket file.
>
> [EMAIL PROTECTED]:~# ls -a /tmp/
> . .. ldm .X11-unix .X6-lock
Check ${thin_client_chroot}/lib/udev/add_fstab_entry:
the socket is maybe /var/run/ldm_socket_*...
And check if the correct ltspfs package is installed on the server and
ldm, ltspfsd on the client's chroot...
I had similar problem at the begining of this month (try google: "Couldn't
read LTSPFS_TOKEN atom"), and I found that the cause of this error is
incompatible versions on the server and client side (maybe the protocoll
of the communication has changed a bit?), AFAIR...
--
Zsolt
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
