|01:56||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50)|
|02:38||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50, Quit: leaving)|
|04:48||mcgwrath has joined IRC (mcgwrath!~mcgwrath@2607:fa49:d53c:eb00:a1a3:421e:492e:38d3)|
Greetings all.. I'm looking for a way that when I perform updates to the server, reboot the server, and recompile my ltsp image for the clients (running chrootless) all of the clients are essentially broken as the various paths are removed once the server reboots. I tried a shutdown -r 00:30 but as the paths were missing, the clients didn't
reboot at that time. Is there some sort of proper process flow for upgrades in a chrootless environment to work? (Currently, I have to manually reboot the clients after an update like that.) Thank you in advance for any hints, tips or tricks!
mcgwrath: update your server, reboot your clients, then reboot your server
*update your server, run ltsp image, reboot your clients, then reboot your server
mcgwrath: actually what you mention should also work. For the rootfs that is; while sshfs (for home) can't survive server reboots
In general keep in mind that nfs can survive a reboot as long as the ltsp image is the same after rebooting.
While if you run `ltsp image` then a single backup is kept; booted clients can still access the now "old" image; but they need to be rebooted to the new image before the server is rebooted
:/ Okay, I'll check it out, but it's like every time I reboot the server I lose the clients, even if the ltsp image is the same... I'll issue a reboot now and prove myself wrong... ;)
mcgwrath: we're talking about new ltsp with nfs, not old ltsp with nbd, right?
And how do you access the clients, via epoptes?
Erm, not sure what nbd is!
Older ltsp 5 technology
Which distro/version are you using?
Finally note that clients can't survive two ltsp image. They can only survive one; then they need to be rebooted to load the new image.
OK, then what I said stands
Can the clients detect a server that has been rebooted and reconnect paths, etc, in nonchroot?
(provided that the image is the same?)
The method that you use to create the image is irrelevant
The result always goes to /srv/ltsp/images/x86_64.img, and is served over NFS
When the server is rebooted, the clients still see the same image, you haven't modified it yet
Well, I'll be damned. It's like you wrote the code for this. ;)
yeah, the clients that were online came back after a server reboot and all is good.
(with those ones.)
erm, 2nd question, (If I may)..
I have a client with a Nvidia card in it and the display gets all weird. I don't want to be using the closed source gfx drivers, but if I change the 'automatic' color profile in Settings -> Device Colour Profiles -> <displayname> and delete the old automatic colour calibration profile and use "Standard Space sRGB", the display is fine. *But* I
can't for the life of me get that change / modification to stay for the users on that fat client!
Nvidia asked you for a password and created an /etc/X11/xorg.conf file. Put it in the image
I have a couple of shell commands for that, but it was really gross and convoluted to perform... The GUI is _much_ easier.
Right on. Thanks again for all your help and support Alkis!
And if you want to selectively install it only for some clients, see the one-before-last example in https://ltsp.org/man/ltsp.conf/
K, I'll dig into that.. When I can remote into that client! :D
But yeah, I got clients identified by MAC address, pass the username and base64 password... It's all pretty nifty!
So thank you.
(I guess I missed the nvidia part right after the mac addresses!) :D ;)
k, again, thanks so much! Night! (1:20AM here.)
|06:26||sunweaver is back|
|07:15||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|07:57||mcgwrath has left IRC (mcgwrath!~mcgwrath@2607:fa49:d53c:eb00:a1a3:421e:492e:38d3, Quit: Client closed)|
|09:44||Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)|
|09:44||Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)|
|11:01||Vercas1 has joined IRC (Vercas1!~Vercas@gateway/tor-sasl/vercas)|
|11:02||Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds))|
|11:02||Vercas1 is now known as Vercas|
|12:17||Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Write error: Connection reset by peer)|
|12:18||Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)|
|14:44||sunweaver is now away: not here ...|
|14:45||Trendzetter has left IRC (Trendzetterfirstname.lastname@example.org, Read error: Connection reset by peer)|
|14:45||Trendzetter has joined IRC (Trendzetteremail@example.com)|
|15:36||sugarbeet has left IRC (firstname.lastname@example.org, Ping timeout: 250 seconds)|
|15:38||sugarbeet has joined IRC (email@example.com)|
|15:44||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50)|
|16:17||XYZ has left IRC (XYZ!~XYZ@89-24-41-33.nat.epc.tmcz.cz, Remote host closed the connection)|
|16:26||XYZ has joined IRC (XYZ!~XYZ@89-24-41-33.nat.epc.tmcz.cz)|
|20:30||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|