See inline.
Στις 04-07-2011, ημέρα Δευ, και ώρα 11:09 -0600, ο/η David Burgess έγραψε: > david@ren:~$ grep david /etc/group > adm:x:4:david > dialout:x:20:david > cdrom:x:24:david > plugdev:x:46:david > lpadmin:x:106:david > david:x:1000:david > david@ren:~$ The output of the `id` command, which shows the groups you belong to, should be the same in both the server and the client. > david@slab:~$ sudo chroot /opt/ltsp/amd64/ adduser david admin > adduser: The user `david' does not exist. In localapps and fat clients, the client dynamically reads the available users from the server, at logon. They don't exist in the chroot. > I would like to have superuser access on the fat client. What is the > recommended way to accomplish this? Do I just need to manually edit > the /etc/group files? Did I mess something up? Most reasons where you would need superuser access, e.g. installing apps, modifying network settings etc shouldn't be needed on fat clients. If you install apps there, they'll be lost on reboot. Install them to the chroot instead. If you modify network settings, your client will hang, as it's using a networked disk. For troubleshooting, you can get root access as usually on LTSP, e.g. with SCREEN_02=shell. If you really need sudo access for a specific user, put that user in /opt/ltsp/i386/etc/sudoers with NOPASSWD there. In a default LTSP installation, authentication doesn't work for localapps and fat clients for security reasons - it was considered insecure to store the user password hash in /etc/passwd on the LTSP client. Continuing with your next mail: Στις 04-07-2011, ημέρα Δευ, και ώρα 13:00 -0600, ο/η David Burgess έγραψε: > 1. The lts.conf option 'NFS_HOME=/home' appears to have the opposite > from expected effect, which is to say that if I include the option in > lts.conf and reboot, my home directory is mounted as a ramdisk and > disappears on reboot. If I omit that option and reboot, 'df' shows my > home directory mounted nfs to the server and changes persist across > reboots. NFS_HOME=/home means "I exported the server /home in /etc/exports. When the client boots, I want it to mount the NFS share to its /home". If that doesn't happen for you, you either configured something wrong, or have hit a bug somewhere. > 2. The lts.conf option "LDM_DIRECTX=True" appears to have no effect. > When rsync'ing /home from my client disc to the mounted nfs share the > ssh and sshfs processes maxed out the CPU before my network or discIO > resources were tapped (~250 Mbit/s with modern SSDs on both ends). > This looked the same with or without the ldm_directx option. LDM_DIRECTX is for X traffic. It has nothing to do with rsync, nfs, sshfs and fat clients. Fat clients use local displays, so they don't cause any X traffic on the network. > 3. User switching does not appear to be supported. If I click on the > power button in the Indicator Applet Session 0.4.6 I get the error > "Unable to start new display: The name org.gnome.DisplayManager was > not provided by any .service files". Indeed LDM does not support user switching. > 4. Once I log out a user, if I log back in again my /home/user > directory does not re-mount via nfs and I get a default login. I can > log in as one user on the system, log out, then log in as another > user, and both see their home directory and profile at their > respective first log in, but subsequent logins by the same user lose > their home. Again, either a misconfiguration or some bug. For example, atl NICs have problems with NFS, they need to use UDP otherwise they hang. > Are these known issues? Are there known workarounds? Unfortunately I > don't see much of this documented on the web at this point, but I'm > willing to troubleshoot if any devs want to work with me. I only see 2 issues that need troubleshooting, the `id` issue and the NFS issue. Try mounting /home from a non-LTSP client to see if you have configured NFS OK. If it works that way, post your /etc/exports and your network cards (lspci -nn -k | grep -A 2 Ethernet) on both the server and the client. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _____________________________________________________________________ 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
