Hi everyone, We use LTSP in our experimental facility, with terminals spread over several floors and used for various uses. Some are just displays, no keyboard/mouse, starting from custom xsession scripts.
I'm struggling with what to do when we run 'ltsp-update-image' on them. At the moment they just trundle along until a squashfs disk access occurs and then they lock up and need hard rebooting.[1] My initial inclination was to put an entry for /sbin/reboot in inetd and just send out a broadcast packet on that port (we're on a private network) to reboot everyone after the image has changed. Then I thought that if /sbin/reboot wasn't cached, this wouldn't work, so I'd need to copy /sbin/reboot to /tmp/reboot at startup and then run /tmp/reboot. Are there any better, less hacky, practices that people are using? - Angus [1] An aside, I have a vague feeling that under older versions a fat client's nbd client would keep being served the old image for as long as that old image file was still open under the corresponding nbd-server process, until that server process ended, so this "squashfs errors / nothing works" situation was avoided. But it seems this has either changed in recent versions (I'm on Ubuntu 12.04) or was never true. ------------------------------------------------------------------------------ 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
