It shouldn't take a few plugs. It might take a few SECONDS for the
device to show up, but not several tries. If it does, this would lead
me to suspect a marginal USB port on the client, or USB hardware that's
not supported well. What kind of mobo do you have in the client?
maybe I was just impatient,
For the terminal I'm testing right now the mother board is
Intel Desktop Board D845GL VA
http://www.intel.com/design/motherbd/va/index.htm
The terminal has four USB ports, two at the front and two at the back
The two at the back sits on the MOBO, the two at the front (which I was
testing) are jsut connected with wires (if that has any significance)
~> mount | grep ltsp
ltspfs on /RAID_SERVER/testuser/Drives/readwrite type fuse
(rw,nosuid,nodev,user=testuser)
ltspfs on /RAID_SERVER/testuser/Drives/tmp type fuse
(rw,nosuid,nodev,user=testuser)
OK, lets check this here. I'm assuming /RAID_SERVER's an NFS mount?
yes
Now, there's absolutely no reason (that I know of) why ltspfs shouldn't
work under NFS. In fact, that's how we use it here:
feniks$ mount
...
palantir:/usr/legal/home on /usr/legal/home type nfs
(rw,addr=192.9.201.36)
ltspfs on /usr/legal/home/sbalneav/Drives/readonly type fuse
(rw,nosuid,nodev,user=sbalneav)
feniks$ cd ~/Drives
feniks$ ls
readonly
feniks$ cd readonly/
feniks$ ls
README.diskdefines casper doc md5sum.txt programs start.ini
autorun.inf disctree install pics start.bmp ubuntu
bin dists isolinux preseed start.exe
So, there's mu ubuntu CD mounted under my home, that's NFS mounted.
Now, just because I'M not having trouble with it, doesn't mean that
others aren't. What happens if you're test user has a home directory on
a local drive?
This could be part of the problem.
I can mount fine for the first user, and nothing for the next users.
Just tested part 10 again, same result as above for a user with $HOME on
local disk.
How long are you waiting between logins? the lbussd takes about 10
seconds to figure out it's controlling X term's gone away, and exit.
If you log out, can you check and see if lbussd's exiting of it's own
accord? Jim McQuillan wrote lbussd, and it's been very stable so far,
but that doesn't mean that there might not be something there that needs
tweaking. Jim, any suggestions?
more than a minute, because I knew it took a little while before lbussd
would shut down.
So now you know why I'm so confused. As mentioned, every thing works
just fine, for the first user after a reboot.
Well, except for the odd permissions on the file.
Could it matter that I took the latest version of fuse from
sourceforge, and used that for installing the fuse libs, that might
not be the same version as is used in the kernel code (I do not know how to
check this)
could be. But for now, the multiple user thing seems to be something
with the perl lbussd.
I think lbussd runs fine, it just does not get any information from the
terminal.
On the lbus_event_handler.sh, there is no interaction with lbussd, because
lbus_event_handler.sh is called from within lbussd.
/daleif
``You cannot help men permanently by doing for them
what they could and should do for themselves. ''
-- Abraham Lincoln
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_____________________________________________________________________
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
