Add "apt-daily" to the RM_SYSTEM_SERVICES lts.conf directive, because now apt runs on boot for your clients, wasting a whole lot of RAM...
This was added in LTSP after Ubuntu 16.04... On 28/04/2017 05:03 μμ, Adam Fischer wrote: > Hello, > > I've been using ltsp with thin clients for a while now, and have > recently been deploying ltsp-pnp with Fat Cleints. > > One of the things that I'm failing to grasp is how the software updates > work. My understanding has been that with fat clients, in order for > them to get updated software, I have to update the ltsp client image. > Well, today, I found that one of my ltsp servers has been doing security > updates automatically. So I looked at which packages were updated, and > I decided to check the versions against what was running on the fat > clients. They were the same. I looked, and the ltsp image on the > server is much older than the update. So in my mind, the software on > the fat client should have been an older version, up until I would have run: > > ltsp-update-image --cleanup / > > So, my question is, how did the software get updated? Does the ltsp > image even get used with ltsp-pnp? It's very confusing, because the > documentation on the Ubuntu Wiki and others indicate that you /have/ to > run the above command to push software updates to the clients. > > I'm asking both out of curiosity, and to maybe clean up my procedures, > as well as have a better understanding for future troubleshooting. > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _____________________________________________________________________ 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
