Re: [Ltsp-discuss] Lubuntu 14.04 ltsp-pnp installation ?
Στις 04/05/2014 09:11 μμ, ο/η asmo.koski...@arkki.info έγραψε: I have tried to install Lubuntu 14.04 LTSP-PNP according to the instructions. But client's do not log in to the desktop. They always return to the login screen again, What should i do? I think I can confirm that with Lubuntu desktop. XFCE, Mate or Gnome Classic are just fine in very same fat client image. I tested Lubuntu 14.04 (LTSP-PNP) (both server and client) in Virtualbox. Best Regards Asmo Koskinen. In LDM, select the xterm session and login to xterm. Then, cat /usr/share/xsessions/lubuntu.desktop, and see the Exec line there, I don't know it off hand. Then write that line in xterm, and check the error messages it produces. -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _ 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
Re: [Ltsp-discuss] Client mounts SD card, but not USB hard drives
Hi, see my answer at 08:53 there: http://irclogs.ltsp.org/?d=2014-03-25 -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs _ 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
Re: [Ltsp-discuss] Busybox with ltsp 5.5 and xubuntu12.04
Στις 28/02/2014 01:26 μμ, ο/η rkwesk_ltsp έγραψε: On 2014-02-28 11:28, Funke, Martin wrote: Does anyone know why it only works this way? The version from the repo ts.sch.gr was deliberately altered Hi guys, no, the ts.sch.gr PPA version is not altered at all, it's just a newer LTSP version (5.5.1) than the one provided in Ubuntu 12.04 (5.3.7), and it's incompatible with it. The newer nbd-server on the server has an export named [/opt/ltsp/i386] while the older nbd-client on the client tries to mount [:ltsp_i386], which is deprecated since 12.10. The same thing would happen if you had a 12.10+ server and a 12.04 chroot. See the various Ubuntu LTSP versions there: http://packages.ubuntu.com/search?keywords=ltsp-server Check the LTSP versions from the server and from your chroot. Then add the ts.sch.gr PPA to your chroot so that both versions match. :) -- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] Change xrandr monitor config based on network MAC after login
Στις 23/01/2014 04:50 πμ, ο/η Graham Innes έγραψε: To solve this, I had someone write a script to issue a xrandr command based on the network MAC address of the machine (similarly to how lts.conf works, but this is executed AFTER login). This should work for both fat and thin clients (thin should use ltsp-localapps when running the script). I've posted it here: https://github.com/gdi2k/mac2xrandr You could implement that script in less than 10 lines, if you wrote it as an LDM rc.d script that checked for lts.conf entries such as [mac:address] XRANDR_COMMAND_0_alkisg=xrandr output DVI-0 --auto --output VGA-0 --auto --above DVI-0 In other words you didn't put the script in the appropriate place and that made it a lot more difficult than necessary. That said, I think that gnome saves the user configuration per monitor in ~/.config/monitors.xml, so you should file a bug report for xfce to do the same. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] I tried to install ltsp-pnp to Linux mint Debian.
Στις 09/01/2014 11:42 πμ, ο/η Takala Tuomas έγραψε: Hello I have tried to install ltsp-pnp to Linux mint Debian. All went ok, until I tried to start client. I got an error message /*NFS over TCP not available*/from (IP address of server). What should I do? Tell Debian to use NBD instead of NFS. I think that's in /etc/ltsp/update-kernels.conf, variable BOOT_METHODS. Then /usr/share/ltsp/update-kernels, and then ltsp-update-image -c / -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] Clients fail to boot: 'Error: socket failed: connection refused'
Στις 09/01/2014 06:07 μμ, ο/η John Hupp έγραψε: Worthy thoughts. I joined about 45 minutes ago, but no one was around then who could push this forward. I see from the log that there was a lot more activity 6+ hours ago. I may rejoin and monitor from this machine and make a fresh initiative later. You just didn't wait long enough, I looked at the channel and saw you 15 minutes after you left. :) IRC needs patience! Also, yes remove all the customizations that you've made, there's no reason to run NBD in port 2000 anymore, you're just making things harder to debug. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] Clients fail to boot: 'Error: socket failed: connection refused' [SOLVED/RECAP]
Στις 10/01/2014 03:32 πμ, ο/η John Hupp έγραψε: But I'm thinking that Alkis probably just did sudo update-initramfs -u and then simply copied the current /boot/initrd.img-3.x.x-xx-generic image to /var/lib/tftpboot/ltsp/i386/. Care to confirm/correct/comment on any of this, Alkis? Yup, everything was like you said it. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] Clients fail to boot: 'Error: socket failed: connection refused'
John you've been trying to troubleshoot this for a long time, whey don't you come over at the LTSP IRC channel for live support to see if we can quickly solve it? It might be something completely unrelated to what you're thinking now, e.g. if you have a router as a DHCP server and you're not using IPAPPEND 3, then some times you'd be getting the NBD connection refused message you were mentioning... http://webchat.freenode.net/?nick=johnhuppchannels=ltspprompt=1 -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] LTSP fails on Ubuntu with mainline kernels?
Στις 28/12/2013 08:37 μμ, ο/η John Hupp έγραψε: But I have not been able to get LTSP to work with any of the mainline kernels I tested: 3.10.1, 3.9.6, 3.8.13, 3.7.5, 3.6.3 all fail. LTSP in Ubuntu is using overlayfs or aufs, and noone of them is mainlined yet, so you can't use a mainline kernel to test LTSP. Just test NBD, don't involve LTSP or netbooting in your tests. Also note that I've seen a problem where NBD wouldn't work for some specific NICs unless I set mtu to 1492 instead of the default 1500. Wishes for a happy new year to everyone, Alkis -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] Where can I review/edit the initramfs init script?
Στις 11/12/2013 11:33 μμ, ο/η John Hupp έγραψε: So for my case with ltsp-pnp, I would understand that the base directory is not /opt/ltsp but /, and that it would default to copying kernels from /boot. Yes, but not exactly. See how it goes: ltsp-pnp is just an easy name to refer to some LTSP administration techniques, it's not a separate implementation of LTSP. The relevant command is: ltsp-update-image -c path For ltsp-pnp, path is /. For NFS or other shares, it could be /path/to/nfs/share. For VMs, it could be /path/to/mounted/vdi/image. In all those cases, /opt/ltsp/images/image-name.img is generated and of course the kernel from path/boot is copied inside it. So yeah, ltsp-pnp copies /boot/vmlinuz inside the image. But then ltsp-update-kernels doesn't care about the initial path. It loop-mounts the image and extracts the kernels from inside it. So there's no ltsp-update-kernels kernel-path option, and for NBD, it wouldn't make sense to have a kernel-path parameter there, to select a kernel that isn't inside the image, because the necessary modules would be missing then. -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] allowing non-sudoer user root access to chroot
You can give them an Ubuntu installation in e.g. a VirtualBox VM, and when they're done, install ltsp-client in it, loop-mount it with vdfuse, and run ltsp-update-image -c /path/to/mounted/vm/disk Στις 11/11/2013 12:47 πμ, ο/η Todd O'Bryan έγραψε: I'd like to set up a second image for my clients to boot from. In particular, several times a year I stay after school and let my students play video games, but I don't want the games clogging up the normal image that we use for class. I'd also prefer not to have to do all the installing and checking on that second image. Is there a way to give a non-sudoer user--a student, actually--access to just that chroot so that s/he can install everything, and then just ask me to run ltsp-update-image when it's time? If not, can the student run ltsp-build-image and ltsp-chroot from his/her account to a chroot inside his/her home folder, and then when everything's set up, can I copy everything to a system-wide location and change ownership to root? -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] Scalability versus Triviality
Hey Asmo, from epoptes, select the clients and run: sudo mount /dev/sda1 /mnt sudo mkdir -p /mnt/Boot/LTSP sudo dd if=/dev/nbd0 of=/mnt/Boot/LTSP/i386.img; reboot Then edit pxelinux.cfg/default so that it reads: APPEND ro initrd=ltsp/i386/initrd.img init=/sbin/init-ltsp root=/dev/sda1 rootflags=ro loop=/Boot/LTSP/i386.img That's the quick method that still uses PXE and loads the kernel+initramfs from the server, but doesn't use NBD at all. It's also possible to install grub 2.0 locally and have it read the kernel+initrd from inside i386.img, but that's a longer how-to... :) Cheers, Alkis Στις 30/10/2013 12:21 μμ, ο/η asmo.koski...@arkki.info έγραψε: There's also the possibility to copy the NBD image locally, if the clients have a bit of local storage, so that the only network traffic to the server is the SSHFS or NFS access to /home. I'm lazy, sorry. No googling around :) Is there any handy howto for that. Best Regards Asmo Koskinen. -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] ltsp-dhcp service script bug
Στις 07/10/2013 04:40 μμ, ο/η emil.kro...@ekrotech.com έγραψε: the script located in /etc/init.d contains wrong name. The red place below should read PDA: conf=$(findConfig $DHCPDARGS) if [ ! $found ]; then DHCPDARGS=$DHCPARGS -cf $conf fi Result is, DHCPDARGS specified in configuration file are not used. Hi, please use launchpad for filing bugs, otherwise it's quite possible that your patch won't get noticed by any of the developers... This is for upstream LTSP bugs: https://bugs.launchpad.net/ltsp Yours is a Fedora bug, but I don't know if Fedora has an LTSP bug tracker, you can still use the upstream URL above though, since that part of the code is in the upstream branch. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] Thunderbird crashing my thin client
Στις 19/09/2013 04:55 πμ, ο/η Michael Pope έγραψε: Is there a way to run thunderbird on the client in a sandbox so that it doesn't crash my whole X session and throw the thin client off the network? I've tried running through ssh -X but that crashed my thin client also. How much RAM does the client have? Thunderbird, Firefox, LibreOffice etc might need e.g. 500 MB of *local* RAM for caching X pixmaps, even if they're running on the server... I.e. it sounds like an out of local memory for X pixmaps issue, so try setting NBD_SWAP=True in lts.conf, and SIZE=512 in /etc/ltsp/nbdswapd.conf. (verify that it works by issuing `free` locally on the client) -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] streaming audio/video to thin-clients
Στις 26/07/2013 09:22 μμ, ο/η Mike Cammilleri έγραψε: Also, iftop on the LTSP server shows ~90Mb/s throughput when I run a youtube video. That translates to roughly 12 Megabytes per second. I would think thats not a lot for the switch? The speed of the ethernet card on the LTSP server is set at 100mb/s, so thats roughly 12 megabytes. So I guess the ethernet card might be my bottle neck? Suppose a user is watching a fullscreen youtube video (it doesn't matter if the video is encoded in low res or not, it's the viewing resolution that matters) in an HD screen. 1920x1080 pixels x 32 bits per pixel x 30 frames per second = 1,990,656,000 bits per second. I.e. for a single client, you'd need 2 Gbps. With X_COLOR_DEPTH=16, just 1 Gbps. If the video wasn't fullscreen but it was viewed in a 480x270 window, then 60 Mbps. On the other hand, if a fullscreen video was displayed with the XVideo technology (e.g. totem or VLC video player), then only the video source resolution would matter, not the viewing resolution (because the scaling then is done client-side), and the bits per pixels would be 12 (that's specific to XVideo), so the required bandwidth would be significantly less: 480*270*12*30=46 Mbps So yeah gigabit at least for the server = switch connection is always mandatory for viewing videos on thin clients. Localapps and LTSP fat clients are much better for video reproduction. -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] Kubuntu 13.04 LTSP-PNP black screen
Στις 25/07/2013 01:18 πμ, ο/η Marco Müller έγραψε: did step by step instructions from help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp except add-apt-repository --yes ppa:ts.sch.gr there are no packages for raring in the ppa? switch on a client, get an IP, tftp ok, kubuntu boot logo appears and then black screen, no cursor, no mouse pointer, nothing client seems to be frozen, have to press the power button for a while. Non-LTS Ubuntu releases don't receive much LTSP testing. In the ts.sch.gr PPA we don't even have support packages for them, although the ltsp-pnp bits should be there since 12.10+. Can I install LTSP-PNP on a Kubuntu system or is it exclusive for Ubuntu? I've heard that kubuntu does have a few problems with LTSP, but nothing that would be specific to ltsp-pnp. So if normal LTSP fat clients would work with Kubuntu (try it), then ltsp-pnp should work too. -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] No ssh into clients due to missing client host keys
Στις 24/07/2013 01:03 πμ, ο/η Jakob Unterwurzacher έγραψε: This means that you won't know the client ssh host key. That's not better than a publicly-known one - either way you can't be sure the box you are connecting to is not spoofed. Not knowing the ssh server public key == trust issue (for the first connection). Also, if anyone (with e.g. a laptop) can read the ssh server private key via the NBD connection, then he can use it for his own ssh server, so knowning the chroot ssh server public key == completely useless. On the other hand, knowing the ssh server private key == privacy issue (for all connections). For example, if I connect to some ssh server and an eavesdropper that has access to the server private key is listening, I believe that he can then monitor the keystrokes (passwords etc) that I type into the ssh shell. Make sure you are using key-based authentification to log into the thin clients. Never use passwords in the thin client - its /etc/shadow is also publicly viewable, and can be used to crack your password. This could then be used to log into thin clients and install keyloggers etc. If done that way I don't see any security issues, even with shared ssh host keys. If my assumption above is true, that a leaked ssh server private key means that the ssh connections are no longer private, then this applies to key-based authentication as well. One other possible implementation that I was thinking of, would be to use some values that are unique for each client as the random seed for the ssh private keys. For example, the client MAC, its output of `dmidecode` etc. Then the LTSP client ssh server host keys would always be the same, and the sysadmin would only need to trust them once. -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] No ssh into clients due to missing client host keys
Στις 21/07/2013 05:47 μμ, ο/η Rüdiger Kupper έγραψε: The reason is that clients have no ssh host keys! They are actively removed during generation of client chroots, due to the following line in /etc/ltsp/ltsp-update-image.excludes: ... My question: How am I supposed to ssh into a running client with its host keys removed? Is this a bug, or am I missing something stupid? sshd in the chroot is disabled by default, for security reasons, i.e. all the clients would have the same sshd host keys, and any non-LTSP client could read them by just mounting the NBD image. If you want to run sshd in ltsp clients even though it's insecure, you can remove the ltsp-update-image.excludes line you mentioned. Or you could put something like this in lts.conf, so that the keys are regenerated on client boot: RCFILE_01=ssh-keygen -A RCFILE_02=service ssh start -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] No ssh into clients due to missing client host keys
Στις 21/07/2013 11:02 μμ, ο/η Rüdiger Kupper έγραψε: Now given this change, and accepted that it is a security measure, let me rephrase my question: - Since ssh login to running clients is a security risk, what other measure can I take to allow remote shutdown of a running client? If you run ssh-keygen on client boot, I don't think there are security issues anymore. Otherwise, you could try http://www.epoptes.org ... -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk _ 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
Re: [Ltsp-discuss] Restricting Internet Access
Στις 04/07/2013 02:46 πμ, ο/η David Burleigh έγραψε: I am in the process of setting up a computer lab with Ubuntu 12.04, LTSP, and a number of thin clients. All is well, except that I cannot figure out how to deny internet access to particular users while allowing internet access to others. Is there a straightforward way to do this on a per user basis? You can do it either with iptables, http://www.cyberciti.biz/tips/block-outgoing-network-access-for-a-single-user-from-my-server-using-iptables.html or with squid and identd, but I don't have a link handy for that one. We're planning to add support for user-based internet blocking in epoptes.org, stay tuned. :) -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _ 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
Re: [Ltsp-discuss] The login keyring did not get unlocked...
Στις 13/05/2013 08:04 μμ, ο/η Thomas Boehm έγραψε: When a user logs in on a client, the login keyring does not get automatically unlocked. Indeed, the LTSP display manager, LDM, doesn't have the ability to unlock the login keyring like other display managers. In LTSP 6, LDM is planned to be replaced by a pam module that will work with any DM, so problems like the one you describe will be solved. I also tried 5.4.x from ppa.launchpad.net/ts.sch.gr/ppa/ubuntu, but can't get it to work at all. I might open a new thread for that... Upgrading from LTSP 5.3 to 5.4 isn't automatic, it needs many manual changes to the LTSP and NBD settings. So unless you're extremely experienced with LTSP, don't use that PPA for LTSP upgrades, but only for clean installations (and only if you really need LTSP 5.4 in 12.04). One quick way to upgrade is to purge ltsp* and nbd-server, rm /etc/ltsp* and /etc/nbd*, then add the PPA, and then install ltsp 5.4. -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _ 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
Re: [Ltsp-discuss] Some questions about LTSP-pnp
Στις 28/04/2013 11:37 μμ, ο/η pierre bertin έγραψε: 1) On dnsmasq There is another dhcp server/bind on the network, so I've just turned it in the /etc/dnsmasq.d/ltsp-server-dnsmasq.conf This works, but is this correct? Sure. You could also remove dnsmasq and use tftpd-hpa if you like. 2) how to turn off hard disks customers I changed LOCALDEV_DENY_INTERNAL_DISKS = True in /var/lib/tftpboot/ltsp/i386/lts.conf but we always see the hard disk In LTSP fat clients, sudoers can see the internal disks, while non-sudoers cannot. This is configurable by policykit. 3)Is there any documentation other than https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp who explains the differences between ltsp-standart and ltsp-pnp No, I don't think so. The code and the packages etc are the same; ltsp-pnp mainly refers to using `ltsp-update-image -c /` to create /opt/ltsp/images/i386.img out of the server disk, and to using dnsmasq in proxydhcp+dns+tftpd mode for easier configuration, but that part is not necessary. -- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _ 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
Re: [Ltsp-discuss] wrong lts.conf used with more than one chroot
Στις 25/04/2013 04:30 μμ, ο/η Thomas Boehm έγραψε: ipappend 3 --- I prefer the second configuration, as it works around the bug(?) of the disappearing ipappend 3 line on every ltsp-update-image... First, to tell LTSP to include ipappend 3, you put IPAPPEND=3 in $CHROOT/etc/ltsp/ltsp-client.conf. Second, ipappend 3 tells pxelinux to include the IP from PXE to the kernel command line, and then udhcpc in the client initramfs reuses it, without doing the usual second DHCP request. The downside there is that the initramfs doesn't know about the boot filename, which usually is /ltsp/i386/pxelinux.0, or, in your case, could also be /ltsp/fatclient/pxelinux.0. $CHROOT/usr/share/ltsp/init-ltsp.d/05-getltsconffile searches for lts.conf in the same place where pxelinux.0 (dhcp boot filename) was downloaded from. So ipappend 3 makes it impossible to have multiple lts.conf files, at least without patching the kernel command line or the chroot, and 05-getltscconffile a bit. E.g. a patch could be to modify /usr/share/initramfs-tools/scripts/init-premount/udhcp so that it uses the nbd parameter in the kernel command line to initialize boot filename, when it's empty. -- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _ 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
Re: [Ltsp-discuss] wrong lts.conf used with more than one chroot
Στις 26/04/2013 04:53 μμ, ο/η Thomas Boehm έγραψε: $CHROOT/etc/ltsp/ltsp-client.conf didn't exist, so I created one. Then I added IPAPPEND=3 and later ipappend 3 instead, after it didn't work. When running ltsp-update-image --arch ... nothing gets added to pxelinux.cfg/default It's a shell file, use IPAPPEND=3, not ipappend 3. That file is executed when a new kernel is installed in the chroot, or when you manually run sudo chroot $CHROOT /usr/share/ltsp/update-kernels That generates $CHROOT/boot/pxelinux.cfg/default, and then ltsp-update-kernels on the server copies it to $TFTP. -- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _ 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
Re: [Ltsp-discuss] Epoptes not responsive after today's Ubuntu updates
Στις 22/02/2013 05:06 μμ, ο/η Todd O'Bryan έγραψε: I'm on Kubuntu 12.04 with a bunch of fat clients. As of yesterday, Epoptes worked fine, but today when I launch it, it brings my whole machine to a halt. I can't click anywhere. Eventually, the machine comes back, but I get a message that the Epoptes window is unresponsive and I'm able to terminate it. That lets me work on the computer again, but obviously, it doesn't let me interact with student computers. Any idea what I did? Todd, please file a question in https://answers.launchpad.net/epoptes so that others can reuse whatever issues we happen to find. Mailing lists aren't very handy for locating/reusing solutions. Also please test running epoptes 1) when no clients are connected, and 2) when clients are connected but no user has logged in -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _ 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
Re: [Ltsp-discuss] Help running nbd-server from inetd
Does anyone know of an easy way to reproduce that issue? (e.g. boot client X, pull network plug, then nbd-server will crash and other clients won't boot anymore...) -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _ 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
Re: [Ltsp-discuss] Epoptes - excluding users or machines from being viewed
Στις 03/12/2012 01:37 μμ, ο/η Matt Johnson έγραψε: All, We're using Epoptes for the first time. I used it this morning to run an English class - really great tool. It helped it all sorts of practical and pedagogical ways. Really good work - thanks. Is there anyway to stop staff accidentally spying on the site manager or a teacher who use our workstations for their daily work and are currently showing up in detected clients. When I fire up Epoptes, I can see the Site Manager emailing from his workstation. Not ideal. Hi, you can disable epoptes-client on a per-user basis by running gnome-session-properties. A dialog similar to the following will appear, you can uncheck epoptes-client from there: http://www.barisione.org/blog-files/2007/02/gnome-session-properties.png Btw, the preferred way to ask epoptes-related questions is https://answers.launchpad.net/epoptes, as it's much easier to search for similar questions there, than searching some mailing list archives. -- Keep yourself connected to Go Parallel: BUILD Helping you discover the best ways to construct your parallel projects. http://goparallel.sourceforge.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
Re: [Ltsp-discuss] On no-chroot LTSP-PNP, use a clients-only .conf for an app?
Στις 22/11/2012 01:49 πμ, ο/η John Hupp έγραψε: The client-server implementation of the UPS manager daemon apcupsd relies on configuring /etc/apcupsd/apcupsd.conf differently on client and server machines. Under standard LTSP5 with a chroot this was accomplished straightforwardly enough. Can I somehow achieve the same result with LTSP-PNP? The usual LTSP way to configure files on the client is to declare variables in lts.conf, for example SCANNER=True, and then to have boot-time scripts that process them, e.g. $ cat /usr/share/ltsp/init-ltsp.d/50-saned # This file is sourced if boolean_is_true $SCANNER ; then [ -w /etc/default/saned ] sed -i -e 's/RUN=no/RUN=yes/' /etc/default/saned fi So what you need is a /usr/share/ltsp/init-ltsp.d/50-apcupsd script. -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _ 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
Re: [Ltsp-discuss] TFTP: Open Timeout error on client (or Transfer timed out error on server)
Στις 20/11/2012 11:21 μμ, ο/η John Hupp έγραψε: I can also run this on the server itself to get a similar failure: $ cd /tmp $ tftp 192.168.1.102 -v -m binary -c get /ltsp/i386/pxelinux.0 If that doesn't work for you, then it's a dnsmasq configuration problem, ... Does LTSP-PNP start its own instance of dnsmasq? If so, can I restart that particular instance, and where does it launch from? No. It just has a dependency on the dnsmasq package, which installs dnsmasq as a service. So, you can use $ sudo service dnsmasq restart etc. I'm only using LTS Ubuntu releases so I've no idea what's wrong with dnsmasq on Quantal, but I fear that this too might be caused by the local resolver hack that Ubuntu devs put in their dnsmasq package: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/959037 I.e. I'm talking about the bind-interfaces etc options that they added in the default dnsmasq installation. If the _only_ thing that you need to do to make dnsmasq work is to switch from network-manager to /etc/network/interfaces, then I'd mention the problem in that bug report above, not in ltsp-discuss. Check also the workaround mentioned in that bug report about commenting #dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf. If you happen to post to ltsp-discuss again, the output of those commands would be interesting: $ sudo netstat -nap | grep dnsmasq $ ps aux | grep dnsmasq $ egrep -rv '^#|^$' /etc/dnsmasq.* -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _ 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
Re: [Ltsp-discuss] Notifications to all users in X sessions?
Στις 01/11/2012 08:29 μμ, ο/η Jay Goldberg έγραψε: Another hint may be that Alkis Georgopoulos' great tool Epoptes http://www.epoptes.org/ offers the option to broadcast messages, the source mayb reveal how this is done. Now that I think about it, though, it will be using the Epoptes client running in the user's X session. Epoptes contains code that can access a user's display even if the script is not run within the user session: http://bazaar.launchpad.net/~epoptes/epoptes/trunk/view/head:/epoptes-client/get-display -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d _ 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
Re: [Ltsp-discuss] Ubuntu 12.04 - problem with old i386 TCs
Στις 31/10/2012 02:05 πμ, ο/η Ondřej Rusek έγραψε: Ubuntu stop support in our kernels for old i386 CPUs (CPU withou cx8 a nd cmov flag). Release 12.04 LTS is for this CPUs unusable. Compiling a kernel won't be enough, other programs might need cmov too. Use Debian Wheezy (which has a compatible LTSP version) either for the chroot only or for the server as well. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _ 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
Re: [Ltsp-discuss] fat client with two eth interfaces
Google for LTSP IPAPPEND=2. This will make your boot interface always eth0. LTSP deliberately leaves network manager to manage the second interface. One way to make that unmanaged as well, is to add a 51-eth1 file similar to chroot/opt/ltsp/i386/usr/share/ltsp/init-ltsp.d/50-interfaces -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] 12.04/LTSP: Yet another thin client consolekeymap problem ?
Στις 24/09/2012 04:30 μμ, ο/η Pierre Yann Baco έγραψε: Still no progress on this one. I'm unable to get a french keyboard with the thin client CONSOLE (CTRL+ALT+F1) with 12.04. I've tried all lts.conf parameters I could think of with no success. There's no problem with LDM and the gnome/unity sessions. sudo chroot /opt/ltsp/i386 dpkg-reconfigure console-setup sudo ltsp-update-image client reboot alt+ctrl+f1 setupcon If the setupcon step is needed, file a bug against Ubuntu, it's not LTSP related. I think that since Ubuntu switched to upstart, it no longer applies the console settings on each tty at boot time. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] using pam_mount instead of sshfs in fat_client
Στις 20/09/2012 06:25 μμ, ο/η Alessandro Dentella έγραψε: This is not working for me, as I reported last week. Even thought I added the FSTAB_1 line (please tell me where it's documented, I only see an example in the source but no doc page), /home is not mounted and sshfs gets in the way. It's documented in the lts.conf manpage: http://bazaar.launchpad.net/~ltsp-docwriters/ltsp/ltsp-docs-trunk/view/head:/lts.conf.xml Ubuntu 12.04 shipped before the manpage was updated though, so while it's there in the code, it's not present in `man lts.conf`. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _ 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
Re: [Ltsp-discuss] Test of mailing list performance
18:43 UTC :) -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _ 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
Re: [Ltsp-discuss] using pam_mount instead of sshfs in fat_client
Στις 19/09/2012 12:21 μμ, ο/η Juan Antonio Martinez έγραψε: - If not, what's the right way to handle an ldap/nfs environment with Ubuntu 12.04's ltsp fat_client ? If you export the whole /home from your NAS server, then you can put e.g. FSTAB_1=server:/home /home nfs defaults,nolock 0 0 in lts.conf. The LTSP clients will then understand that /home is already mounted and won't try sshfs. And, if you have LDAP configured on your server, you can just let the clients use their default SSH-based authentication. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] using pam_mount instead of sshfs in fat_client
Στις 19/09/2012 02:50 μμ, ο/η Juan Antonio Martinez έγραψε: Not sure if this solution work for us: Yup, with the additional info you gave it probably doesn't suit you out of the box, so you'd need to patch the ltsp scripts a bit. - We use pam_mount to handle not only user home, but other user/group dependent directories (some of then my mean of cifs-mount) E.g. you can create a script to conditionally set LOCALAPPS_EXTRA_MOUNTS based on the user/group that logs in. And another script for nfs /home/user mounting upon login. - There is a collateral problem in server: sshd limits the number of simultaneous incoming connections by mean of MaxStartUps configuration variable. When 30+ students try to simultaneous login into fatclients, ltsp server refuses more ssh connection for authentication You can easily increase that from sshd_config. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] Fat clients, ACL and NFS: need some explanation...
Στις 05/09/2012 10:48 μμ, ο/η Alessandro Dentella έγραψε: I set in lts.conf:: NFS_HOME=/home NFS_HOME is deprecated. If your LTSP is recent enough, try something like this in lts.conf instead: FSTAB_1=server:/home/home nfs defaults,nolock 0 0 Put acl and whatever else you need there. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] Incomplete shutdown on some clients (shutdown hangs/freezes)
Στις 25/08/2012 09:27 μμ, ο/η John Hupp έγραψε: A simple press of the power button does not turn off the machine at that point. I have to press and hold it 5 seconds or so. This is a BIOS setting. Press [del] when the machine starts, and select Instant off or Wait 5 seconds before poweroff. It's not related to the operating system that you use. On the Edubuntu network, all clients have to invoke Shutdown from the desktop and from the login screen. After choosing Shutdown from the desktop (and then presenting a dialog for Shutdown or Restart), it drops back to the login screen, and there one chooses Preferences: Shutdown. [Very tedious, but that's not my real interest in this post. And as a footnote, the server shuts down cleanly after the two clicks on the desktop. I reported that problem in https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/491940, you can comment there if you want. One other behavior that was of interest to me but that I did not thoroughly document was that even on machines where Shutdown hangs, it seems generally to be the case that Restart does not hang. The machine proceeds smoothly to POST and reboot. The machine does not power off problem is related to acpi/kernel. You can verify that it isn't related to ltsp by booting the client with a CD or usb stick. You can report that upstream to the kernel, see https://wiki.ubuntu.com/Bugs/Upstream/kernel for instructions. Or failing that, can I insert a splash screen at the end of the shutdown process something like Windows 95/98 used on machines where it could not execute a complete shutdown automatically? (The screen said something like It is now safe to turn off your computer.) It's not very easy, and it isn't LTSP-specific, it's distro specific. If you decide that you want to do that, you'll need some Ubuntu-specific mailing list or other means of communication (generally bug reports in launchpad are a good method). -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] Unreliable DHCP server: No DHCP offers received on LTSP client
Στις 24/08/2012 06:00 μμ, ο/η John Hupp έγραψε: A wikipedia article (https://en.wikipedia.org/wiki/Systemd) provides a tempting brief on systemd as a replacement for init. And if isc-dhcp-server fails to start during boot in some cases because of a dependency or timing sort of issue, then systemd sounds promising as a longer-term solution. But note the IF. At the moment I don't know why isc-dhcp-server fails to start during boot on this test system. And apart from why it doesn't start during boot, I don't know if such a problem is widespread. Others with more experience may know -- I'm a newbie with Linux. It's possible that you have configured network manager with a user connection, i.e. that your network is only started after a user logs in on the server. If so, either make it a system connection (check [x] available to all users), or use /etc/network/interfaces instead. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] Running/Installing via WINE in the chroot
Στις 22/08/2012 12:44 πμ, ο/η David Trask έγραψε: Hi, Running Edubuntu 12.04. We use NWEA TestTaker for our testing here at our school. I'd like to run it as a localapp...therefore I need to be able to install it into WINE (it's a Windows programbut it runs fine in WINE as we've run it as a regular app in the past...it just give us some issues that I think would be solved by running it as a localapp). Is there a way I can get a GUI from the chroot to be able to install this program via WINE? Any ideas? 1) Install the program for some user, e.g. administrator. It'll be installed in his own home folder, in ~/.wine/drive_c/Program Files... 2) Install wine in the chroot. Don't install the program in the chroot. Run ltsp-update-image, reboot a client and login as the user that installed the program. 3) Run: ltsp-localapps xterm. An xterm will open. There, run: wine ~/.wine/drive_c/Program Files/...your program. So, since the user home folder is accessible with SSHFS, you don't need to install the wine programs in the chroot, you can create a launcher that runs `ltsp-localapps full-path-to-the-exe`. ...but how to do that for all users? Well, you either need to do it for each user separately, or if it's a portable program that can be ran without installation, copy the folder from ~/.wine/drive_c/Program Files/your program to /opt/ltsp/i386/usr/share/your program, run ltsp-update-image, and create a launcher for ltsp-localapps /opt/ltsp/i386/usr/share/your program -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] possible to use an include statement in lts.conf?
Στις 17/08/2012 11:42 μμ, ο/η David Trask έγραψε: The idea behind this...is that in my lab here at this school...for the very young kids (kindergarten) I prefer to have all the lab machines log in automatically...and then once they are gone and the older kids come in, I want to revert to normal operation. In the past I simply swapped lts.conf files using the cp command to copy over lts.conf with another containing the appropriate entries. I think I could make this cleaner and easier by simply referencing another file using the include statement. Any ideas? No, lts.conf currently doesn't support include statements. You could put all your snippets in /etc/ltsp/config.d/default /etc/ltsp/config.d/tc1 /etc/ltsp/config.d/tc2 ... and create a generate-lts-conf script that conditionally merges the ones you want each time into /var/lib/tftpboot/ltsp/i386/lts.conf. Also note that LDM_USERNAME defaults to HOSTNAME, so in the examples you pasted, you don't need it, and that if LDM_PASSWORD is always q, then you can put it under [Default], even for machines that don't use autologin. Finally, check the LIKE directive, in helps avoiding repetition. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] Choppy scrolling in Chromium on terminal
One reason why scrolling might be very choppy is when the clients have very little RAM and they need to use swap all the time. See the last paragraph in http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/view/head:/client/Debian/share/ltsp/init-ltsp.d/50-rm-system-services about some services that you can disable (from lts.conf) to free as much RAM as you can. 256 MB RAM is good enough for thin clients out of the box, 128 MB RAM might need some more fine-tuning. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] Verifying NBD Swap is active?
Στις 12/08/2012 12:24 πμ, ο/η John Hupp έγραψε: But if nbdswapd.conf format mimics lts.conf, then when the instruction says size ... for each client, it may mean that nbdswapd.conf should like more like: [Default] size=128 It's a shell-sourceable script, so no header should be put there, and the variable name should be in CAPS, and no spaces should be put around the '=' sign. SIZE=128 Note that it's a sparse file, so that won't affect the initial, real size, but only the maximum file size. And if the client really needs 128 MB swap and tries to allocate it, it'll crash with SIZE=128. So you don't really have a reason to specify the swap size unless someone is trying to crash your server by abusing the swap export. The edubuntu wiki page you mentioned needs to be updated for 12.04, e.g. the NBD_PORT section is obsolete since NBD is now using the IANA assigned port 10809 and name-based exports instead of port-based. Finally, to verify if nbd swap is active, on the client, run: ltsp-localapps xterm and on that xterm, cat /proc/swaps free -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] need syntax for some xrandr options in lts.conf
Στις 02/08/2012 01:12 μμ, ο/η Marco Müller έγραψε: got here a terminal with dualmonitor setup on the terminal start ltsp-localapps xterm: marco@ltsp23:~$ xrandr --output HDMI1 --mode 1920x1080 --scale 1x1 --output HDMI3 --mode 1360x768 --scale 1.406x1.406 --same-as HDMI1 to set correct resolution, scaling, clonemode for both monitors can I set this in lts.conf? For distros with LTSP = 5.3.7, just put XRANDR_COMMAND_0=xrandr all your params here -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] How to blacklist a module for the LTSP clients
File a wishlist bug request in LTSP to introduce a BLACKLIST_MODULES=module1,module2,... lts.conf directive: https://bugs.launchpad.net/ltsp Other than that, the reason you couldn't find some specific how-to for blacklisting modules on LTSP, is that the blacklisting process itself isn't LTSP-specific. So in general, you search in google whatever you want without the LTSP part, and then you follow the same modify image/update image etc steps that you described in your last post. So for your other problem, the first thing to test is if the clients can shutdown when they're NOT booted as LTSP clients. If they can't, you should google about it until you learn where to file the relevant bug report, e.g. in acpica or in the kernel itself. The package maintainers then would direct you on what info they need in order to solve the bug. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] SCREEN_07=shell console font size
Στις 20/07/2012 06:44 μμ, ο/η rob έγραψε: Hello We use SCREEN_07=shell for cli / console use. However the fonts are tiny.The console displays as a rectangle taking up just 1/4 to 1/3 of the screen depending in the hardware. Any suggestions on what to try to increase the font? We're looking to emulate a 25 line by 80 character wide character terminal. `dpkg-reconfigure console-setup` in the chroot, and you might also need a `setupcon` call on some RC script if you see that it doesn't apply on boot, Ubuntu has had problems with that for years now. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] having issues with SCREEN_07=shell
On Thu, Jul 19, 2012 at 1:22 PM, Robert Fantini r...@fantinibakery.comwrote: the screen hangs forever at the screen that shows Ubuntu Does anyone have a suggestion? In /opt/ltsp/i386/etc/init/ltsp-client-core.conf there's a line that reads: /bin/plymouth quit --retain-splash || true I'm guessing that this is supposed to stop plymouth but retain the image on screen, so that there's a smooth transition to X. And since you're not using X, there's no code to clear the retained plymouth image. I'd suggest for you to file a bug in https://bugs.launchpad.net/ubuntu/+source/ltsp in order for some developer to see/fix that part of the code, and in the meantime to remove quiet splash plymouth:force-splash vt.handoff=7 from /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] new LTSP install in Kubuntu 12.04 alot of bugs / problems
Στις 18/07/2012 01:06 πμ, ο/η Marco Müller έγραψε: Now I chanced my network a bit and installed ltsp-server and dnsmasq and I didnt remove the network-manager. Now Im in trouble. I set some parameters in /var/lib/tftpboot/ltsp/amd64/lts.conf: LDM_DIRECTX = true ... If you're using dnsmasq in proxydhcp mode, then symlink /var/lib/tftpboot/ltsp/amd64/lts.conf to /var/lib/tftpboot/ltsp/i386/lts.conf so that the clients find your lts.conf. Also, don't forget the [Default] on top. To verify that your clients correctly get lts.conf, run: ltsp-localapps xterm and there getltscfg -a Installed xbmc as a local app in the chroot then on the terminal I tried to start a KDE-session: error cant find /usr/bin/startkde On which terminal? Local? Did you install KDE in the chroot? In the LDM-session checkbox KDE-session was gone After complete remove xbmc in the chroot i could choose KDE-session and login XBMC installs a session at /usr/share/xsessions/XBMC.desktop. So the (new) LTSP logic at $CHROOT/usr/share/ltsp/ltsp_config.d/20fatclients assumes you want the client to behave as fat, so it doesn't read the server sessions (KDE) anymore, only the local ones (XBMC). To avoid that, specify LTSP_FATCLIENT=False in lts.conf. on the terminal ltsp-localapps xterm in xterm ping heise.de unknown host DNS doesnt work anymore so I set in lts.conf: DNS_SERVER = 192.168.0.2 SEARCH_DOMAIN = fritz.box did not work See the remarks about lts.conf above. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] LTSP server questions
Στις 29/06/2012 09:57 μμ, ο/η Derek Schuurman έγραψε: Hi, We have been using LTSP for a school and library computer lab of roughly 35 clients. For the most part, LTSP has worked well, but we have had some issues with lag when many students are using the lab. This is particularly the case when users are running flash-based multi-media pages. ... 2) We have tried running client browsers as a local app - this greatly helped with the lag issue, but we ran into complications with helper apps ie. when users click on a .doc or .pdf file, the browser attempts to launch the helper apps locally (LibreOffice or PDF readers etc.) and fails. We dont want to install every possible helper app as a local app. If you use LTSP fat clients, then all apps, even helper apps, open normally. Then you don't even need a good server, as fat clients use no server CPU/RAM, but only its disk. So you could easily netboot 35 clients with a much lighter server than the one you already have. https://help.ubuntu.com/community/UbuntuLTSP/FatClients https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] ubuntu 12.04 ltsp-pnp nbd problem
Στις 13/06/2012 11:27 πμ, ο/η Peter D Knight έγραψε: client boots into initramfs dmesg shows unable to read squash super block added this to /etc/inetd.conf 2000stream tcpnowait nobody /usr/sbin/tcpd /usr/sbin/nbdrootd /opt/ltsp/images/i386.img Remove it, in 12.04 nbd-server is ran as a service instead of from openbsd-inetd, and listens in the IANA-assigned port 10809. Send the output of: * cat /proc/cmdline, from the client initramfs * cat /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default, from the server If you have an /opt/ltsp/i386 chroot from a non ltsp-pnp setup, move it to another place, e.g. sudo mv /opt/ltsp/i386 /opt/ltsp/i386.older and run: sudo ltsp-update-kernels because otherwise ltsp-update-kernels copies the older /opt/ltsp/i386/boot/pxelinux.cfg/default to the TFTP directory, instead of extracting the correct one from /opt/ltsp/images/i386.img[loop-mounted]/boot/pxelinux.cfg. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] ubuntu 12.04 ltsp-pnp nbd problem
Στις 13/06/2012 11:52 πμ, ο/η Jan Middelkoop έγραψε: Also interesting that your /etc/nbd-server/conf.d/ltsp_i386.conf is different than mine. For me the section is called [ltsp_i386] and for you it's [/opt/ltsp/i386]. I wonder why that is. I added that part in upstream LTSP after 12.04 was released. The reasoning was that it's now possible to control the NBD path from the DHCP root-path option, same as it always was with NFS. So now one can e.g. create an additional chroot in /opt/ltsp/i386-nvidia-clients and control with DHCP which clients get that instead of plain i386, with no other configuration changes at all. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] xfreerdp and Ubuntu 12.04
Στις 11/06/2012 09:05 μμ, ο/η David Burgess έγραψε:
On Fri, Jun 8, 2012 at 5:39 PM, Alkis Georgopoulosalk...@gmail.com wrote:
It appears that xfreerdp started segfaulting if $HOME is unset.
It used to work some months ago when I last tested it.
Try this:
sudo editor /opt/ltsp/i386-original/usr/share/ltsp/xinitrc
and after this line:
. /usr/share/ltsp/ltsp-client-functions
put this:
export HOME=${HOME:-/root}
That worked. Thank you. I will file a bug report.
db
Cool, pushed in
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2334
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_
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
Re: [Ltsp-discuss] xfreerdp and Ubuntu 12.04
Στις 09/06/2012 02:39 πμ, ο/η Alkis Georgopoulos έγραψε: It appears that xfreerdp started segfaulting if $HOME is unset. It used to work some months ago when I last tested it. Try this: sudo editor /opt/ltsp/i386-original/usr/share/ltsp/xinitrc ...I meant i386, not i386-original there. To reproduce the problem in any system, not necessarily an LTSP client, run: unset HOME xfreerdp localhost == Segmentation Fault (core dumped) ... xfreerdp crashed with SIGSEGV in freerdp_get_config_path -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] xfreerdp and Ubuntu 12.04
Could you try with SCREEN_07=xfreerdp -f --ignore-certificate --no-nla -d gprc -u dburgess 172.21.34.1 and post the output of hexdump -C /proc/pid of xfreerdp/cmdline hexdump -C /proc/pid of xinit/cmdline hexdump -C /proc/pid of xinitrc/cmdline both for the normal lts.conf method, and for the xterm/manually ran xfreerdp method? -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] xfreerdp and Ubuntu 12.04
It appears that xfreerdp started segfaulting if $HOME is unset.
It used to work some months ago when I last tested it.
Try this:
sudo editor /opt/ltsp/i386-original/usr/share/ltsp/xinitrc
and after this line:
. /usr/share/ltsp/ltsp-client-functions
put this:
export HOME=${HOME:-/root}
save, exit, and run:
sudo ltsp-update-image
If it works, file a bug in the xfreerdp package,
and I'll commit the workaround in LTSP.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_
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
Re: [Ltsp-discuss] ltsp-pnp i386 xfreerdp
Start with SCREEN_07=xterm Run xfreerdp from there, with any command line you want. Then put that command line in SCREEN_07=xfreerdp params Don't include any RDP* variables at all, not even the server. Is it working this way? -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] Slightly OT: how to let someone take over your terminal?
Graphics mode sharing = You: 1) Port forward 5500 on your router 2) apt-get install xvnc4viewer 3) xvnc4viewer -listen Student: 1) apt-get install x11vnc 2) x11vnc -connect your-ip Console sharing === You: 1) Port forward 5500 on your router 2) apt-get install socat 3) socat tcp-listen:5500,keepalive=1 stdio,raw,echo=0 Student: 1) apt-get install screen socat 2) socat SYSTEM:sleep 1; exec screen -xRR ra$$,pty,stderr tcp:your-ip:5500 screen -l -S ra$$ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] ltsp-pnp i386 xfreerdp
Στις 08/06/2012 12:58 πμ, ο/η John Gallias έγραψε: SCREEN_07=xterm LTSP boots, fully launches xterm: no input. Cannot provide any input to xterm. Can still access a console on CRTL + ALT + F1. Move your mouse over the xterm window. If your still cannot provide input, your problem isn't related to the LTSP screen scripts, it's something else. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] power button press no longer shuts down client
Στις 05/06/2012 12:41 πμ, ο/η David Burgess έγραψε: Greetings, For the past several releases of Ubuntu I have install acpid in the chroot for the sole reason that this permits the thin client to power off when the power button is pressed. I'm now testing Ubuntu 12.04, and although acpid is installed in the chroot, pressing the power button no longer results in a system shutdown or power off. Is this expected? Is there a simple way to revert to the old behaviour? Is there something I can do to troubleshoot this? Thanks. https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/998966 -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] Simpler method for fat/thin client setups
The ltsp-pnp method of maintaining LTSP installations without a chroot is now upstream in LTSP. It's no longer a separate package; all that's needed is to run ltsp-update-image --cleanup / and that will generate an /opt/ltsp/images/i386.img image out of the server disk contents, while excluding sensitive data like user accounts and ssh keys. The newer LTSP version required is currently available for Ubuntu 12.04 from a PPA and it should be available later on for Debian Wheezy as well. More info: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] Does LTSP on Ubuntu 12.04 default to fat clients?
When the clients boot, this script: /usr/share/ltsp/ltsp_config.d/20fatclients runs this command: find /usr/share/xsessions/ -name '*.desktop' \ ! -name Xsession.desktop If any xsession files are defined there, i.e. if gnome or KDE or other DE is installed in the chroot, the client is considered a fat, otherwise a thin. And of course if that autodetection doesn't work for you, you can manually set this in lts.conf: LTSP_FATCLIENT=False -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] ltsp in debian
Στις 16/05/2012 05:27 πμ, ο/η Quiliro Ordóñez έγραψε: So LTSP does not work on Pentium III as a client? This would make LTSP non-viable for me. I thought only X worked on the clients. Is X that heavy? LTSP works fine on Pentium II with 128 MB RAM. But some apps like firefox or openoffice make heavy use of local X RAM in order to speed things up and prevent roundtrips to the X server. E.g. I've seen firefox running on thin client (i.e. on the server) using 300 MB RAM of *local* X RAM to cache images. There's an option to disable that, but of course it'll slow firefox down a bit, read more in this bug report: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/137764 In order for your clients not to crash you can enable an e.g. 512 MB NBD swap file, read your distro docs about enabling NBD swap in LTSP. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] ltsp-remoteapps with ltsp-pnp
Στις 26/04/2012 11:33 πμ, ο/η Gymhaan Rechenzentrum έγραψε: Do I have to install/configure/run/ ltsp-remoteappsd on the server? You need REMOTE_APPS=True in lts.conf. And again: ssh does not work correctly, I can connect to the server but get a wrong password answer. Even though you don't need it, if you want to troubleshoot that, paste the exact command you use and the exact output. E.g. ssh user@server (server is a special hostname, all LTSP clients know the server with that name) -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] ssh on ltsp-pnp
Στις 26/04/2012 03:17 μμ, ο/η Gymhaan Rechenzentrum έγραψε: debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to ts [127.0.1.1] port 22. debug1: Connection established. You're connecting to 127.0.1.1, i.e. to your fat client itself, not to the server. Please stop testing ltsp-pnp and wait a few weeks until it's merged upstream. About the nbd-server limits, no, its man page mentions that: -M Specify the maximum number of opened connections. If this parameter is not specified, no limit is set. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] ltsp-pnp
Στις 25/04/2012 11:19 πμ, ο/η Gymhaan Rechenzentrum έγραψε: is there a flag I can set to force clients to be thin? Hi Roland, you probably missed my previous reply in the list where I already answered your question: http://www.mail-archive.com/ltsp-discuss@lists.sourceforge.net/msg40404.html Or again can I define sets of machines that work as thinclients even if they have plenty of ram? [mac:addresss] LTSP_FATCLIENT=False -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] ltsp-pnp at our school
Στις 24/04/2012 02:05 μμ, ο/η Gymhaan Rechenzentrum έγραψε: but now I found your ltsp-pnp for 12.04 which is absolutely great !!! Hi Roland, *** To all: please don't test ltsp-pnp anymore *** As mentioned in previous mails, it's being merged upstream, and will be ready in a couple of months. I'll notify the list with details once the updated tools (e.g. ltsp-update-image --export-root) are ready. The following are unrelated to ltsp-pnp, they affect all fat client installations: Second is that I want to use unity as default desktop but it has to be ubuntu 2D. When I select this everytime at the ldm it works fine, but how can I set this to default In lts.conf: LDM_SESSION=gnome-session --session=ubuntu-2d Can I change the limit up to which the clients behave as thinclients rather than fatclients? [Default] FAT_RAM_THRESHOLD=600 Or again can I define sets of machines that work as thinclients even if they have plenty of ram? [mac:addresss] LTSP_FATCLIENT=False Cheers, Alkis -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _ 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
Re: [Ltsp-discuss] Simpler method for fat/thin client setups
Στις 19/04/2012 10:33 πμ, ο/η Asmo Koskinen έγραψε: Never mind Asus Eee 900 keyboard problem. If the problem is that the numlock is on, try uninstalling the numlockx package. Otherwise we'd need more info to see what's wrong with it, `setxkbmap -print` etc etc. What is your further testing plan for ltsp-pnp? How I can help? The simplicity of ltsp-pnp also results in a small code base; I don't have many more things to commit. I'm considering thought whether it's now a good time to put it upstream... -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _ 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
Re: [Ltsp-discuss] epoptes fails to broadcast on a client who has logged out and logged in again
Στις 10/04/2012 02:43 μμ, ο/η Suraj Kumar έγραψε: I not only updated both server (epoptes) and chroot (epoptes-client) but also ran epoptes-client -c on the client thinking that it must be done. Would that have broken this? You also need to update epoptes-client on the server. If you're still having a problem, a) run epoptes from a gnome-terminal on the server, b) run epoptes-client from a gnome-terminal on the thin client, and paste any errors that you see in the output. Another place to look for errors is /var/log/epoptes.log. Attach all those 3 logs so that we can check that the problem is. Also, for troubleshooting, IRC is much easier than mailing lists, you can find us in #ltsp (see the epoptes Help menu IRC option). Cheers, Alkis -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _ 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
Re: [Ltsp-discuss] Simpler method for fat/thin client setups
A first release of ltsp-pnp is available, for more details see: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp Warning, don't use it on production machines, it's beta-quality yet. In a test I made, I installed Ubuntu 12.04, then ltsp-pnp, and ran ltsp-publish-image. In 10 minutes the compression finished and an 1.5 Gb /opt/ltsp/images/pnp.img was generated with about the same contents as my server, and I was able to boot thin and fat clients with it. No server reboot was necessary (apt locking was implemented). A screenshot with the PXELinux menu automatically generated by ltsp-pnp (I deliberately had a very complex setup): http://imagebin.org/index.php?mode=imageid=207317 -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _ 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
Re: [Ltsp-discuss] epoptes fails to broadcast on a client who has logged out and logged in again
Στις 07/04/2012 12:19 μμ, ο/η Suraj Kumar έγραψε: Hi, Epoptes fails to broadcast to a client who has logged out and logged in Hi Suraj, you're probably talking about a bug that was fixed in http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/247 and released in Epoptes 0.5.0. Please update both your server and chroot to the latest epoptes versions, and see if the problem persists. If you ever want to file an epoptes bug, you need to go to that page: https://bugs.launchpad.net/epoptes You'll need to open a launchpad account if you don't have one already. -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _ 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
Re: [Ltsp-discuss] Simpler method for fat/thin client setups
Στις 06/04/2012 02:31 μμ, ο/η Jay Goldberg έγραψε: I'm sure that you are aware that LVM will do snapshots as well? Maybe this can be used to avoid the reboot? For starters, we'll try running ltsp-publish-image while the server is running. I believe that in most cases that will run fine, and I'll try to put some code to disable package updates or cron jobs at that point. I also have code for `ltsp-publish-image --revert` to revert to the last exported image, in case problems are found in the new one, so that will also help in maximizing client uptime and avoiding server downtime. Only if we see in practise that a server reboot is necessary, we'll resort to `grub-reboot --set-the-ltsp-publish-image-default`. Even if sensitive server files bleed over to the client image, doesn't Ubuntu's security settings block other users anyway? NBD or NFS exported root disks are generally insecure. I won't go into details, I'll just say that while it needs some expertise (and a non-LTSP client owned by the hacker) to gain access, we should remove all sensitive data from the published disk. In /usr/share/ltsp-pnp/publish.d/ there are some scripts that take care of that; sysadmins can add their own in /etc/ltsp/publish.d. ltsp-publish-image creates a COW dir and mounts with overlayfs/aufs the server / there, so programs like deluser can be ran in a chrooted environment to remove users, regenerate certificates etc (while not touching the server / at all). I'll publish an initial ltsp-pnp version in a few days, and more cleanup scripts will be added over time. It's just a matter of pinpointing the sensitive data and erasing it, so I don't think that we'll hit a problem that we won't be able to overcome. -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _ 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
Re: [Ltsp-discuss] Simpler method for fat/thin client setups
Στις 02/04/2012 09:55 πμ, ο/η David Burgess έγραψε: This is the first I've heard of this, so please excuse my ignorance. Is this going to be the single method going forward or will do you plan to preserve the old way for some foreseeable future? This package will only be available in a PPA. It's not related to ltsp-upstream and won't be included in any distros for a long time, and certainly not until any security concerns are resolved. And even then, it will be just an alternative way to maintain LTSP, not the new way to maintain LTSP. I admin a network of 80 or so thin clients that all use LTSP to boot and run RDP, so here are my concerns with the new system you're describing. The target user group is small computer labs where a simple GUI-based method to maintain a Linux fat chroot is preferred over the console-based one. Since you're using RDP, you definately don't need it, so you can completely ignore the related mails. My second concern is comparatively minor. I would really hate to have to reboot with every image update though, as things tend to happen here in a day at work, and it sure is nice to be able to tweak something on the fly and not have to bring everybody down. That's why it targets small computer labs, where it's not a very big problem to reboot the server at the end of the day if an image update is necessary. Actually one could do that when the server is running too; but he's risking filesystem and package inconsistencies if he's installing programs etc while running the export image script. In the future, when a compressed BTRFS file system will be an option for LTSP servers, there won't be a need for a server reboot as it will be possible to use BTRFS snapshots. With those, there won't even be a squashfs step necessary, the image exporting will be instant. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _ 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] Simpler method for fat/thin client setups
Now that the ltsp-server and ltsp-client packages are allowed to be installed simultaneously (LP: #950945), I thought of an extremely simple method to install and maintain LTSP fat/thin computer labs that should be appealing to certain setups like small school labs. We'll probably start using it in Greek schools in a month, and I'd like to ask the community for feedback on where this could lead to problems, and also on whether there's interest in an internationalized version of the ltsp-server-pnp package that we'll develop to automate this. The installation steps for this new method will be: 1. Install your server normally with any DE you prefer (Gnome, KDE, XFCE, LXDE...). Also install and configure on the server any applications that you want to have in your thin/fat clients. 2. Add the repository for the yet-to-be-developed ltsp-server-pnp package, which automatically installs and configures ltsp-server, ltsp-client, dnsmasq, PXE menus etc for you. 3. Reboot your server and select Recovery console in the grub menu. From the recovery menu that will appear, select Generate LTSP image. This will create the /opt/ltsp/images/i386.img NBD image, and it will need about 5-10 minutes to complete, without requiring Internet connectivity. That's all, you can then boot your server normally and start your thin/fat clients. If you need to update your chroot in the future, you just do any changes you want directly on the server (add/remove apps or settings) and follow step (3) again. Pros: * Great simplicity. As you've seen, there's *no LTSP chroot involved*, so no ltsp-build-client step, no ltsp-chroot install packages step, no manually transfer gconf mandatory settings to the chroot step. Cons: * Loss of flexibility. The server needs to be the same arch as the clients, so you'll probably want the i386-pae kernel in your server. You can't even have different packages installed in your server than in your thin/fat clients. But you can still have e.g. apache, mysql, sshd etc installed on your server and put them in the RM_SYSTEM_SERVICES lts.conf directive so that they don't run in your clients. No, that doesn't put any additional RAM overhead, your clients can still have as low as 128 MB RAM no matter how many services you have installed on your server. And of course in bigger setups you can use a separate server for NFS/apache/whatever, and only keep the LTSP-related services in the server where ltsp-server-pnp runs. * Security concerns. E.g. the clients will have the same sshd keys as your server. But I think that in step (3) above, the security-sensitive data can be regenerated or omitted. And of course /home, /srv, /opt, and user's entries in /etc/passwd and /etc/shadow will be omitted too in the NBD image. * Finally, your server needs to be rebooted to update the NBD image, so some downtime is involved. This will be avoided in the future when BTRFS snapshots will be available. Thoughts? And, does anyone care about an internationalized Ubuntu Precise/Debian Wheezy package for this? -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _ 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
Re: [Ltsp-discuss] X_COLOR_DEPTH=16 by default for thin clients
Στις 26/03/2012 10:05 πμ, ο/η Alkis Georgopoulos έγραψε: By default, X_COLOR_DEPTH is 32 for thin clients, which means that a 320x240 youtube video needs 73.728.000 bps bandwidth (30 fps, 32 bpp). Setting X_COLOR_DEPTH=16 for thin clients makes that video need exactly half the bandwidth, i.e. 36.864.000 bps. Sorry, calculations were based on the original video size and not on the flash player applet size, which is what matters. Here are some more accurate results, based on the usual 640x350x30fps youtube flash applet: X_COLOR_DEPTH=32: Bandwidth=640x350x30x32=215.040.000, i.e. up to 4 clients on gigabit X_COLOR_DEPTH=16 Bandwidth=640x350x30x16=107.520.000, i.e. up to 9 clients on gigabit Flash replacer plugin which uses XVideo which always uses 12bpp and depends on the original video size instead of the applet size (https://addons.mozilla.org/el/firefox/addon/161869/): Bandwidth=320x240x30x12=27.648.000, i.e. up to 36 clients on gigabit XVideo playback needs the same bandwidth on fullscreen videos too, but of course on bigger original video resolutions that quickly increases. Unfortunately those plugins have other problems and don't always work. Let's hope browsers support XVideo as an HTML5 video playback option. :) -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _ 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
Re: [Ltsp-discuss] X_COLOR_DEPTH=16 by default for thin clients
Στις 27/03/2012 09:34 πμ, ο/η Ben Green έγραψε: Almost definitely, unless it's a really old LCD one. You can see the difference even from the default LDM login screen. At 16-bit, the blue background is noticeably barred with distinct colour bands. $ file /opt/ltsp/i386/usr/share/ldm/themes/ltsp/bg.png /opt/ltsp/i386/usr/share/ldm/themes/ltsp/bg.png: PNG image data, 640 x 480, 8-bit/color RGBA, non-interlaced The blue LDM background only has 256 colors, i.e. 8 bpp, in order to be 4k size, that's why it appears banded no matter your display color depth. It would make no difference at all if you displayed it in 8 bpp, 15/16 bpp, or 24/32 bpp displays. Also note that its small 640x480 resolution and bad gtk dithering made the matters worse; we increased its resolution to 1024x768 in latest versions, it should display a bit better now. In other words, don't use the ldm theme to judge the difference between 16 bpp and 32 bpp. Login, open some photo or video, and check there. There is a difference, but it should be barely noticable. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _ 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
Re: [Ltsp-discuss] X_COLOR_DEPTH=16 by default for thin clients
Στις 27/03/2012 10:58 πμ, ο/η Ben Green έγραψε: That's simply not true Alkis, with 16-bit colour I see bands, with 32-bit no bands. I can provide pictures if you like. Its not a complaint about the picture quality, I'm just saying the difference is very visible. Please see the next paragraph of my answer, which mentions gtk dithering. :) Please, do provide pictures, by opening /opt/ltsp/i386/usr/share/ldm/themes/ltsp/bg.png in an image viewer *after* login. :) And if you try to maximize that image instead of seeing it in its default 640x480 size, then make sure that your viewer also supports decent dithering. The login screen dithering part is a separate issue of the general talk about 16 bpp vs 32 bpp quality. E.g. if we used a .jpg instead of an 8bpp .png, you shouldn't be seeing any bands at all even on login screen. That's why I'm insisting that any comparison should be done after login. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _ 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
Re: [Ltsp-discuss] X_COLOR_DEPTH=16 by default for thin clients
A person contacted me off-list (as he had some problems posting to the list), and reported that he tried X_COLOR_DEPTH=16, and it made XVideo not working for him with the following chipset: Intel Corporation 82865G 8086:2572 (rev 02) Kernel driver in use: i915 Kernel modules: i915 That very old graphics card is a known headache: https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes On Ubuntu Lucid, I even had to download a patched kernel and add a PPA to make a non-LTSP client boot with it. I think most of its problems were solved in recent kernel + xorg versions though, and even that person said that he'll try to disable XVideo and start using X_COLOR_DEPTH=16 from now on, so I don't think it's enough to revert to the old behavior. If others see similar problems with 16 bpp, we can talk about it again. Cheers all, Alkis -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _ 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] X_COLOR_DEPTH=16 by default for thin clients
By default, X_COLOR_DEPTH is 32 for thin clients, which means that a 320x240 youtube video needs 73.728.000 bps bandwidth (30 fps, 32 bpp). Setting X_COLOR_DEPTH=16 for thin clients makes that video need exactly half the bandwidth, i.e. 36.864.000 bps. Of course that doesn't only affect videos. Any thin clients screen updates need half the bandwidth with X_COLOR_DEPTH=16. Less bandwidth means faster responses, less CPU usage (especially with the default LDM_DIRECTX=False), and support for more clients with the same CPU/LAN constrains. So I propose a change in upstream LTSP to set X_COLOR_DEPTH=16 by default, if: * LTSP_FATCLIENT is not set (fat clients would still default to 32), * LOCAL_APPS_MENU is not set (so 32 for localapps browsers too), * X_COLOR_DEPTH is not set at all (so X_COLOR_DEPTH= in lts.conf reverts to the old behavior). Is that what most LTSP users would like? Comments, please... :) If not, then I'll implement an X_COLOR_DEPTH=auto instead, which would give the above behavior (16 on thins, 32 on fats/localapps) only when requested from lts.conf. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _ 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
Re: [Ltsp-discuss] X_COLOR_DEPTH=16 by default for thin clients
Στις 26/03/2012 12:04 μμ, ο/η Ben Green έγραψε: If not, then I'll implement an X_COLOR_DEPTH=auto instead, which would give the above behavior (16 on thins, 32 on fats/localapps) only when requested from lts.conf. To be more positive in my response, the above would be an excellent addition. What's the negative side of making that the default, so that the average user wouldn't have to read all lts.conf options, detect that one, create an lts.conf and set it there, before enjoying its speed benefits? People that have a reason (which one?) to not want that can still set X_COLOR_DEPTH= in lts.conf to go back to the old behavior. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _ 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
Re: [Ltsp-discuss] X_COLOR_DEPTH=16 by default for thin clients
Στις 26/03/2012 12:54 μμ, ο/η Ben Green έγραψε: I don't think this setting -color depth- should be conditional, if there's going to be a default, it should be the same for all, otherwise it gets confusing. I strongly disagree; the default should be to try hard to work in all cases. That's true in other lts.conf options already (e.g. NBD_SWAP was always automatically enabled for clients with =48 MB RAM), and in other environments too (e.g. if gnome-shell doesn't work for you, you automatically get gnome-fallback; if unity-3d doesn't, you get unity-2d; if your screen is small enough, you get kde-plasma-netbook instead of the standard one; etc etc). Some chipsets respond very differently to different color depth settings, and so it would be bad for beginners to find that when one setting changed when another changed, possibly resulting in seemingly broken clients. For example, we have clients which just don't have the RAM for 32-bit modes. We still might want to run local apps on them though. Changing the bit depth when we changed to a local apps set up would cause X not to start suddenly. I'm not proposing to force X_COLOR_DEPTH=32 when LOCAL_APPS_MENU=True. I'm proposing to leave the default empty value there, which in this case would default to 16bpp. We also have old intel clients where OpenGL only works (albeit in a limited fashion) on 16-bit color modes. A conditional change in bit depth would be confusing in this case. Why doesn't any GL now work? These are only two examples but I'm sure there's more. In all the cases you mention, the automatic color depth would either solve the problem, or not have any bad effect at all. Can you think of an example were it would do harm? Its not really a big deal for me, I can, and do, set the bit depth for the installs I do, but I don't think the change is productive. The simplest solution is the current one, set a reasonable default and let the administrator choose. A note in the documentation would be more appropriate if we want administrators to be choosing appropriate bit depths. If an administrator has 30 thin and 30 fat clients, he'd like it if they worked as well as possible out of the box, instead of having to put [mac:address] sections in lts.conf for each one of them. Having the conditional as part a =auto option is great though. snip ...otherwise it gets confusing. In both cases, the auto logic would be documented, so it wouldn't be confusing. The only question is if we want the default value to be auto or not. Since you mention that the auto default wouldn't have any bad effects for you, and all the others mentioned that it would have good effects for them, let's wait to see if it'll actually have bad effects for anyone here. If not, we can make it the default. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _ 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
Re: [Ltsp-discuss] X_COLOR_DEPTH=16 by default for thin clients
Στις 26/03/2012 02:07 μμ, ο/η Ben Green έγραψε: The situations where having =auto as the default would cause problems are: 1. Where clients don't support 16-bit colour and are not using local apps. Have you ever actually seen clients that don't support 16 bpp modes, or is that theoretical? 2. Where clients don't support 32-bit colour but want to use local apps. Again, that's not a problem. X_COLOR_DEPTH=auto won't affect those clients. X_COLOR_DEPTH=auto means: 1) X -depth 16, or 2) X without a -depth parameter at all. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _ 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
Re: [Ltsp-discuss] X_COLOR_DEPTH=16 by default for thin clients
Στις 26/03/2012 01:50 μμ, ο/η Oliver Grawert έγραψε: we had it as default for years, you should dig on launchpad iirc there were bugs that made us change to 32 ... Oli the hardcoded X_COLOR_DEPTH=16 was removed in commit http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/979 with no bug reports mentioned. In the LTSP changelog, there's this bug referenced: LP: #149006 (default to 24bit colordepth) But in that bug report, the reported actually says the opposite, that setting X_COLOR_DEPTH=16 fixes his problem (comment #11). We've been using X_COLOR_DEPTH=16 in 250+ schools here for a couple of years, I haven't heard any real world problems with it. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _ 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
Re: [Ltsp-discuss] X_COLOR_DEPTH=16 by default for thin clients
After some IRC discussion, here's what will be implemented: By default (X_COLOR_DEPTH= or X_COLOR_DEPTH=smart), thin clients get 16 bpp, and fat clients get the xorg default depth (usually 32). No special exceptions for thins with localapps. X_COLOR_DEPTH=auto reverts to the old behavior, i.e. default depth for all. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _ 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
Re: [Ltsp-discuss] X_COLOR_DEPTH=16 by default for thin clients
Στις 26/03/2012 08:25 μμ, ο/η Alkis Georgopoulos έγραψε: After some IRC discussion, here's what will be implemented: ... Sorry, some code paths depended on X_COLOR_DEPTH being numerical if unset, so the following got committed instead: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2149 X_SMART_COLOR_DEPTH=True by default sets 16 bpp for thin clients (no exceptions for localapps), and one can set it to false to revert to the old behavior of letting xorg decide the color depth for thin clients. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _ 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
Re: [Ltsp-discuss] Best way to connect to server
On 14/03/2012 04:51 μμ, Pierre AUSSAGUEL wrote: ...The NIC is a PCMCIA One. What is the best way to connect to the server ? You only need to transfer the LTSP kernel and initrd to your local disk. Copy the kernel from /srv/tftp/ltsp/i386/vmlinuz etc to a new /ltsp/ dir on your client. Then create grub entries (from /etc/grub.d/40-custom or so) for this kernel, with the same boot parameters as specified in your server's /srv/tftp/ltsp/i386/pxelinux.cfg/default. If special steps were needed for your PCMCIA card to work, do them in your server LTSP chroot to get an initramfs that supports it. -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _ 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
Re: [Ltsp-discuss] high disk i/o and server load during user logon (sftp-server)
Logging in in LTSP fat clients using sshfs (sftp-server) takes about twice longer than if NFS_HOME=/home is set in lts.conf. Maybe you'd want to consider switching to NFS for the user homes. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _ 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
Re: [Ltsp-discuss] high disk i/o and server load during user logon (sftp-server)
Στις 15/02/2012 02:24 πμ, ο/η john έγραψε: I assume the main difference between sftp-server and the NFS_HOME=/home is that the NFS connection won't be encrypted? I think NFS4 does support encryption, if you want it. NFS_HOME_OPTIONS allow you to specify mounting options. Personally I'm using NFS3. -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _ 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
Re: [Ltsp-discuss] both italc and epoptes broadcast stopped working after installing djbdns
Στις 30-01-2012, ημέρα Δευ, και ώρα 12:57 +0530, ο/η Suraj Kumar έγραψε: btw, openssl should be listed as a dependency of epoptes-client because in a stock install I get the following output: $ sudo chroot /opt/ltsp/i386 epoptes-client -c /usr/sbin/epoptes-client: line 132: openssl: command not found epoptes-client ERROR: Failed to fetch certificate from localhost:789 The `epoptes-client -c` option is there to help you transfer the certificate instead of doing so manually (e.g. with scp or with a usb stick like iTalc suggests), so openssl is not required for the normal epoptes-client use. I'll put openssl in the Suggests: list, thanks! :) -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _ 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
Re: [Ltsp-discuss] Debian and nVidia Vanta
Στις 30-01-2012, ημέρα Δευ, και ώρα 12:52 +0200, ο/η asmo.koski...@arkki.info έγραψε: Alkis - I googled that you have problems with nVidia Vanta, too, but you fixed them? I translated this page with google: http://alkisg.mysch.gr/steki/index.php?topic=3808.0 So I need 'nouveau' and prevent module 'vga16bf'? And in Debian I put that 'video = nouveau' in 'pxelinux.cfg/default', on Debian path is '/srv/tftp/ltsp/i386/pxelinux.cfg/default'? Vanta worked out of the box in Ubuntu for me, but that vga16fb problem made it hang sometimes. So the fix in pxelinux.cfg/default is to prevent the hangs. If it doesn't work out of the box in Debian for you, then it's another problem. In the end Vanta works fine but sometimes I can see some pixels left by the mouse movement (bad mouse redraws). -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _ 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
Re: [Ltsp-discuss] both italc and epoptes broadcast stopped working after installing djbdns
Στις 30/01/2012 08:47 πμ, ο/η Suraj Kumar έγραψε: md5sum /opt/ltsp/i386/etc/epoptes/server.crt md5sum: /opt/ltsp/i386/etc/epoptes/server.crt: No such file or directory In the http://www.epoptes.org/installation page, you missed the part about copying the server certificate to your chroot. Now, run the following commands on your server: sudo chroot /opt/ltsp/i386 epoptes-client -c sudo ltsp-update-image And reboot your clients. After that you should be able to broadcast to them even before they login. -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _ 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
Re: [Ltsp-discuss] both italc and epoptes broadcast stopped working after installing djbdns
Στις 28-01-2012, ημέρα Σαβ, και ώρα 16:07 +0530, ο/η Suraj Kumar έγραψε: I installed djbdns. After installing the broadcast screen feature of both iTalc as well as epoptes stopped working. ... My suspicion is that avahi has been broken. Epoptes doesn't use avahi. What's the output of these commands, if you run them on your server? dpkg-query -W epoptes sudo chroot /opt/ltsp/i386 dpkg-query -W epoptes-client md5sum /etc/epoptes/server.crt md5sum /opt/ltsp/i386/etc/epoptes/server.crt sudo netstat -nap | grep :5500 -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _ 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
Re: [Ltsp-discuss] dist-upgrade of chroot fails on linux-image-3.0.0-15-generic
Στις 26-01-2012, ημέρα Πεμ, και ώρα 14:51 +, ο/η Todd O'Bryan έγραψε: I'm trying to upgrade my chroot and it won't update the kernel. Here's the output: ... /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). ... Errors were encountered while processing: linux-image-3.0.0-15-generic linux-image-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Anyone have any idea why this is happening and how to get around it? That's happening because /dev isn't mounted, and grub-probe needs it. Run `mount --bind /dev /opt/ltsp/i386/dev` before entering your chroot, or uninstall grub from the chroot or even blacklist it so that it never gets installed again. -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _ 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
Re: [Ltsp-discuss] Epoptes in windowed broadcast mode?
Στις 26-01-2012, ημέρα Πεμ, και ώρα 08:20 +0530, ο/η Suraj Kumar έγραψε: Can epoptes do windowed broadcast of session? Has anyone managed to do this? Hi Suraj, hehe, nice coincidence! Someone requested that yesterday, and it was implemented in http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/145 and it will be available in the next epoptes version. Unfortunately that added 2 more translatable strings, so translators should again visit https://translations.launchpad.net/epoptes/ in a couple of days when launchpad will pick up those new strings. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _ 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
Re: [Ltsp-discuss] ltsp client configuration
Στις 14-01-2012, ημέρα Σαβ, και ώρα 15:03 +0100, ο/η stefania zanette έγραψε: In my opinion the problem is not video card or driver configuration because PIVs login without any problem to the first user called mario01 and to the administrator called mariofiore but they don't login with other users. On the contrary PIII login with all users. That's a frequent problem caused by compiz (package: compiz-core), which is installed and used by default in Ubuntu. The reason it only appears on specific users is indeed the appearance tab settings, if one logs into another PC and sets it to None, he disables compiz for his account. To disable compiz for all users, run this command on your server, it takes effect immediately, so you can go ahead and try logging in with any user after issuing it: sudo gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set /desktop/gnome/session/required_components/windowmanager metacity If that command doesn't solve your problem, here's is how to undo it and re-enable compiz: sudo gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --recursive-unset /desktop/gnome/session/required_components -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 _ 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
Re: [Ltsp-discuss] avoiding bloating the image for fat clients
Στις 02-01-2012, ημέρα Δευ, και ώρα 10:52 -0500, ο/η Todd O'Bryan έγραψε: In other words, can I just start with the bare minimum image and then install all the other programs I want somewhere and mount that from the server? Why? What are you trying to gain? The fat client image isn't loaded in the client RAM. Similarly to USB disks, the client only reads the sectors it needs each time. So you can have e.g. 5 Gb fat images without any problem at all. Now if you put those 5 Gb to the server file system instead, because of lack of compression (NBD can be compressed, see the wiki), the same folders would need about 12.5 Gb, and that would make the fat client disk access about 2.5 times slower because of the lack of compression, plus a couple of times even more slower because of the ext/nfs/whatever overhead (NBD/squashfs is block-based and read-only, so it's more efficient). So to sum up, if you did what you want, you'd get about 5 times slower disk access, and your only benefit would be that ltsp-update-image would finish a few seconds sooner. -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _ 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
Re: [Ltsp-discuss] avoiding bloating the image for fat clients
Στις 02-01-2012, ημέρα Δευ, και ώρα 11:29 -0500, ο/η Todd O'Bryan έγραψε: You'd also be able to install a new program or make a tweak without having to rebuild the image and restart the clients, wouldn't you? Not to my knowledge. Run `dpkg -L firefox` and see where the firefox package puts its files. All over the file system. I don't think there's any easy way to expose all those directories to the clients, AND to rebuild any icon/menu/whatever caches dynamically, etc etc. Maybe the /usr/local/* dirs can be utilized for this, but I doubt it would be painless. I also still haven't figured out a good way to install/update programs that use a GUI installer/update. Especially annoying are Eclipse plugins If they're per-user plugins, they get installed in /home/username/.something, so you just install them normally from a user account. If they're per-system plugins, and no .deb packages exist for them, just mount --bind whatever dirs you need from the server to your chroot, and run that program while chrooted. You do have X access there, I don't suppose eclipse requires anything more fancy like system dbus to install plugins, does it? For the future, it is planned that LTSP chroots will be bootable read-write from a client or from a virtual machines, so that one can administer the chroot graphically (e.g. with virtualbox). -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _ 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
Re: [Ltsp-discuss] LTSP FAT Client thin client problem
Στις 10-12-2011, ημέρα Σαβ, και ώρα 22:34 +0100, ο/η luca predari έγραψε: then asked if there was a way to invoke the heekscad from fatclient to the server What you're looking for is called remote apps and it's the opposite of local apps. You basically set REMOTE_APPS=True in lts.conf, and then you run `ltsp-remoteapps heekscad` from the fat client, and it runs on the server. There's also REMOTE_APPS_MENU_ITEMS which is similar to LOCAL_APPS_MENU_ITEMS, if you need it. -- Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _ 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
Re: [Ltsp-discuss] Nvidia ION2 fat clients mixed with other hardware
Στις 25-11-2011, ημέρα Παρ, και ώρα 20:34 -0500, ο/η Jay Goldberg έγραψε: I've found that as fat clients these aren't quite as snappy as I'd like them to be. With regards to video performance, fat clients are *exactly* as fast as local, standalone installations. You can have 3D acceleration, VDPAU and whatever else your driver offers. 3D acceleration over the network (for thin clients) is more difficult to achieve and much, much slower. They only difference, performance-wise, to local installations, is in the disk access: * Fat clients have e.g. 1 Gbps shared disk (network) bandwidth. That's usually a bit faster than one (non SSD) new hard disk. So if one serves multiple clients with 1 Gbps connection, that would be slower than local installations. * But, since most of that read-only network disk is already cached on the server from previous requests, there's no disk rotation latency involved, which is a big plus in disk speed. It's somewhat like having an SSD disk on the server. * Finally, if one is using NBD with compression enabled, that's about 10 times faster than NFS and a few times faster than local disks, since more data fits on the same bandwidth. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, 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-novd2d _ 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
Re: [Ltsp-discuss] Problem with Epotes in LTSP-Environment
Στις 21-11-2011, ημέρα Δευ, και ώρα 17:10 +0100, ο/η Hans-Peter Lackner έγραψε: Hi! Yes! x11vnc is in the chroot. = /usr/bin/x11vnc In the console of my ltsp-root after starting epoptes and trying to control a session: -- output -- VNC Viewer Free Edition 4.1.1 for X - built Apr 9 2010 18:41:55 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Mon Nov 21 17:03:27 2011 main:Listening on port 5500 -- output -- How did you install it? Where should I start looking for error logs or something?? You shouldn't need to do anything that's not in the installation page. x11vnc needs to be installed in the server for student screen monitoring, not in the chroot, but it should get automatically installed as it's in the Recommends: section. If you have a firewall, is 5500 open? To see the client-side error messages, either check the user's ~/.xsession-errors, or just open a gnome-terminal from the user session on the thin client, and run: /usr/sbin/epoptes-client If you need live assistance/troubleshooting, you can also find us in the IRC channel from the epoptes Help menu. Cheers, Alkis -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, 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-novd2d _ 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
