Tim- I had noted the same difference on my setup, but making that change didn't do any good. I since switched it back, and as you said, "it just decided to work" when I made the change to a different version of FUSE. It does seem like the switch to a local terminal helps - watching the response to a drive key being plugged in is worth the effort.
-Krishna On Fri, 16 Jun 2006, Timothy Legge wrote: Alistair Crust wrote: > We have come up with something quite interesting here regard the "second > user problem". > > First, just to clarify we have tried this on both our not-so-wyse > machines and our optiplexes (these use pxe and boot "out the box system" > with NO modification what so ever, unlike the wyse that have a altered > kernel and initrd and /lib/2.6.19.1/modules) > > lbuscd seems to take a long time to load on boot on our clients. > The second logon problem persists and it seems to be on the client - > first logon after boot, USB stick works perfectly but on subsequent > logons (anybody) it always fails. A server restart does not help so it > looks like something on the client is not working as it should. > > After further investigation it seams that a manual fire of > lbus_event_handler.sh works like a charm. (both add and remove) I can > only presume that the code that fires that script has a problem after > the first person has logged out. But why I don't know. > Hi I was just looking at a terminal that had the second login problem. I may have resolved it. After the fix I was able to login multiple times as different users and each time the usb drive showed up. Now, this may be totally by coincidence but: The usb drive would not work when I got there and I had noticed similar issues (a week or so ago) to those reported: the second login seemed unable to find the usb drive. What may (or may not) have fixed my issue: 1) Change to the terminal console (<Alt>+<F2>) could be <F1> or others 2) type: hostname 3) look at the returned value (for me it was DELL-001) 4) Return to X on the client (<Alt>+<F1>) could be <F2> or others 5) Open a terminal 6) type: echo $DISPLAY (for me it was DELL-001.ltsp) 7) note that http://wiki.ltsp.org/twiki/bin/view/Ltsp/LTSP-42-LocalDev#Step_10_Does_your_DISPLAY_variab mentions that they must match exactly 8) vim /etc/dhcpd.conf 9) modify the host entry for DELL-001 to be DELL-001.ltsp 10) service dhcpd restart 11) reboot the client 12) test multiple logins As I said, I am unsure if this fixed it or whether it just decided to work for a little while and I did not have time to revert and try it the old way. If your client has issues, give it a try and see if this might be a fix... Tim _____________________________________________________________________ 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 _____________________________________________________________________ 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
