LTSP 5 is in minimal maintenance mode
The new LTSP is hosted at https://ltsp.github.io

IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 19 August 2019   (all times are UTC)

00:02pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
00:07pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Ping timeout: 272 seconds)
01:15pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
01:19pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Ping timeout: 246 seconds)
03:58pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
04:02pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Ping timeout: 245 seconds)
04:03shored has left IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi, Read error: Connection reset by peer)
04:03shored has joined IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi)
05:03Justin59 has joined IRC (Justin59!cdb6851f@205.182.133.31)
05:12
<Justin59>
can the host be a different version of linux than the client(s)? Like Ubuntu and Bliss OS. Looking to have one server serve multiple zero client devices.
05:14os_a has joined IRC (os_a!~Thunderbi@195.112.116.22)
05:15Justin59 has left IRC (Justin59!cdb6851f@205.182.133.31, Remote host closed the connection)
05:34statler has joined IRC (statler!~Georg@p5489731F.dip0.t-ipconnect.de)
05:43
<alkisg>
Justin59, sure :)
05:48ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:05ZAJDAN has joined IRC (ZAJDAN!~zdenek@77.48.149.75)
06:29pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
06:29pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Remote host closed the connection)
06:30pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
06:39kjackal has joined IRC (kjackal!~quassel@adsl-221.109.242.68.tellas.gr)
06:40pavars_ has joined IRC (pavars_!~pavars@105.235.144.22)
06:43pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Ping timeout: 244 seconds)
06:51asmok has joined IRC (asmok!~asmok@62-78-149-154.bb.dnainternet.fi)
06:53asmok has left IRC (asmok!~asmok@62-78-149-154.bb.dnainternet.fi, Client Quit)
06:54asmok has joined IRC (asmok!~asmok@62-78-149-154.bb.dnainternet.fi)
06:59
<asmok>
I have LTSP 19.08 installed in Virtual Box (Ubuntu 18.04 Mate, Debian 10 Mate, Debian 10 LXDE). Virtual Box Client works with all of them. But not with Debian 10 Gnome. Here is screenshot from Virtual Box Client stopped with Debian 10 Gnome.
06:59
https://ltsp.fi/HOWTO/VirtualBox_LTSP_Client_19_08_2019_09_17_21.png
07:00
<alkisg>
Hey asmok
07:00
Now let's see that new debugging in practice!
07:00
So, it immediately says the problem is in configure_gdm, looking...
07:01
asmok: open /usr/share/ltsp/client/init/55-display-manager.sh
07:02
Compare the configure_gdm function with: https://github.com/ltsp/ltsp/blob/master/ltsp/client/init/55-display-manager.sh
07:02
Do you have that new version, or something older?
07:02
<asmok>
latest one, just a moment
07:03
<alkisg>
Ah never mind I got it
07:03
It's the `set -e` restrictions
07:03
Just before line 30, put this: return 0
07:03
Then save and run: ltsp initrd
07:03
Then reboot client, see if it works
07:09pavars_ has left IRC (pavars_!~pavars@105.235.144.22, Remote host closed the connection)
07:10pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
07:11pavars_ has joined IRC (pavars_!~pavars@105.235.144.22)
07:12
<asmok>
Yes, it works now. Thank you.
07:13
This is latest one: 19.08-1~201908181341~ubuntu18.04.1
07:13
<alkisg>
Yey, it told us where it broke, and it didn't even need ltsp-update-image to get fixed. LTSP19 ftw! :)
07:14
asmok: do you have time to do a bug report with this, so that others feel better starting bug reports?
07:14
As LTSP19 is very new, I think seeing the troubleshooting process may help them
07:14
<asmok>
I can do that
07:14
<alkisg>
If you can, go there, and upload the image too
07:14
!ltsp-bug
07:14
<ltsp>
I do not know about 'ltsp-bug', but I do know about these similar topics: 'ltsp-nfs'
07:14
<alkisg>
!ltsp-issues
07:14
<ltsp>
ltsp-issues: https://github.com/ltsp/ltsp/issues is where you file bug reports or feature requests that can be addressed from the LTSP code base. See also !community-issues for more general LTSP questions or discussions
07:14pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Ping timeout: 248 seconds)
07:15
<alkisg>
Great; mention the problem, upload the image, and I'll reply and upload a fixed ltsp
07:15
Thanks!
07:15
<asmok>
But as I said before, this LTSP19 is something ;-)
07:25
<fiesh>
great if ltsp is github hosted -- git repositories are much more convenient to use as a means of updating than most other solutions
07:26
<alkisg>
fiesh: I'm developing and using ltsp using a github repository; you'd just git clone to a folder, and symlink it to /usr/share/ltsp, and it should work :)
07:26
I mean, I don't have the .deb installed at all
07:26
So ltsp19 is very suitable for distributions that don't have .debs too
07:30asmok has left IRC (asmok!~asmok@62-78-149-154.bb.dnainternet.fi, Quit: Leaving)
07:38
<fiesh>
yes, that's great
07:39
and also versioning and patching is much better with git
07:39
life without git is basically pointless at this stage of evolution and will cease to exist sooner than later
08:10ltsp_user21 has joined IRC (ltsp_user21!984dcbe3@baron-von-blubba.u-ga.fr)
08:11statler has left IRC (statler!~Georg@p5489731F.dip0.t-ipconnect.de, Remote host closed the connection)
08:20ltsp_user21 has left IRC (ltsp_user21!984dcbe3@baron-von-blubba.u-ga.fr, Remote host closed the connection)
08:31pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
08:35pavars_ has left IRC (pavars_!~pavars@105.235.144.22, Ping timeout: 245 seconds)
08:41kjackal has left IRC (kjackal!~quassel@adsl-221.109.242.68.tellas.gr, Quit: No Ping reply in 180 seconds.)
08:42kjackal has joined IRC (kjackal!~quassel@adsl-221.109.242.68.tellas.gr)
08:47kjackal has left IRC (kjackal!~quassel@adsl-221.109.242.68.tellas.gr, Client Quit)
08:49kjackal has joined IRC (kjackal!~quassel@adsl-221.109.242.68.tellas.gr)
08:49statler has joined IRC (statler!~Georg@gwrz.lohn24.de)
09:12pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
09:13pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Remote host closed the connection)
09:14pavars has joined IRC (pavars!~pavars@105.235.144.22)
09:14pavars_ has joined IRC (pavars_!~pavars@balticom-198-107.balticom.lv)
09:18pavars has left IRC (pavars!~pavars@105.235.144.22, Ping timeout: 246 seconds)
09:26pavars has joined IRC (pavars!~pavars@105.235.144.22)
09:29pavars_ has left IRC (pavars_!~pavars@balticom-198-107.balticom.lv, Ping timeout: 245 seconds)
09:37pavars_ has joined IRC (pavars_!~pavars@balticom-198-107.balticom.lv)
09:40pavars has left IRC (pavars!~pavars@105.235.144.22, Ping timeout: 258 seconds)
10:12pavars_ has left IRC (pavars_!~pavars@balticom-198-107.balticom.lv, Remote host closed the connection)
10:18ZAJDAN has left IRC (ZAJDAN!~zdenek@77.48.149.75, Quit: Konversation terminated!)
10:18ZAJDAN has joined IRC (ZAJDAN!~zdenek@77.48.149.75)
10:20pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
10:28kjackal has left IRC (kjackal!~quassel@adsl-221.109.242.68.tellas.gr, Ping timeout: 245 seconds)
10:31pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Remote host closed the connection)
11:04shored has left IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi, Read error: Connection reset by peer)
11:04shored has joined IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi)
11:13gdi2k has joined IRC (gdi2k!~gdi2k@180.190.170.240)
11:16pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
11:21pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Remote host closed the connection)
11:27kjackal has joined IRC (kjackal!~quassel@ppp-94-66-220-142.home.otenet.gr)
11:35pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
11:58pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Remote host closed the connection)
11:58pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
12:08pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Remote host closed the connection)
12:10pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
12:14Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:20pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Remote host closed the connection)
12:29wfw has joined IRC (wfw!~Thunderbi@WEGC203087.UNI-GRAZ.AT)
12:30pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
12:40pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Remote host closed the connection)
12:47wfw has left IRC (wfw!~Thunderbi@WEGC203087.UNI-GRAZ.AT, Quit: wfw)
12:48wfw has joined IRC (wfw!8f32cb57@WEGC203087.UNI-GRAZ.AT)
12:59pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
13:09pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Remote host closed the connection)
13:31cristiano^206-36 has joined IRC (cristiano^206-36!bf24ced1@191.36.206.209)
13:33wfw has left IRC (wfw!8f32cb57@WEGC203087.UNI-GRAZ.AT, Remote host closed the connection)
14:06pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
14:20pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Remote host closed the connection)
14:21shored has left IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi, Read error: Connection reset by peer)
14:21shored has joined IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi)
15:32kjackal has left IRC (kjackal!~quassel@ppp-94-66-220-142.home.otenet.gr, Ping timeout: 244 seconds)
15:52Hyperbyte has joined IRC (Hyperbyte!~jan@middelkoop.cc)
15:52
<Hyperbyte>
Good afternoon. :-)
15:54
<alkisg>
Heya Hyperbyte, how are things up there?
15:54
<Hyperbyte>
Things are good! :-)
15:55
Did I mention we moved to a new house?
16:16
<alkisg>
Great, hope it's a big cozy one
16:21pavars has joined IRC (pavars!~pavars@balticom-198-107.balticom.lv)
16:25pavars has left IRC (pavars!~pavars@balticom-198-107.balticom.lv, Ping timeout: 248 seconds)
16:47
<Hyperbyte>
alkisg, yeah it is. :-) More big than cozy, but the latter we can work on. So I haven't mentoined it before?
16:47
Then I guess I haven't mentoined Kim and I are getting married? :-)
16:59vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
17:33shored has left IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi, Read error: Connection reset by peer)
17:33shored has joined IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi)
18:02
<alkisg>
Hyperbyte: congrats!!! Let's also hear about kids next year! ;)
18:11* alkisg ponders how to call the new PASSWORD_ALKISG="base64pass" parameter, that will be used for passwordless logins and autologins...
18:13
<alkisg>
Maybe PASSWORDS_x="alkisg base64pass vagrant anotherpass"
18:17
Hrm the username can contain non latin characters etc, so it definitely must be a string, not part of a variable name
18:19
Maybe with a colon, PASSWORDS_x="alkisg:base64pass vagrant:anotherpass"
18:20
Or they could go in a separate file, not in ltsp.conf...
18:36statler has left IRC (statler!~Georg@gwrz.lohn24.de, Remote host closed the connection)
18:50* alkisg settles with: PASSWORDS_DEVS="alkisg:cGFzc3dvcmQK vagrant:" That means that alkisg can login with "enter" instead of typing a password and get sshfs home, and vagrant can login with "enter" and get either nfs or local or tmpfs home (no ssh/sshfs authentication; guest accounts etc)
18:50
<alkisg>
To encode the passwords, one would run: echo "password" | base64
18:51
<vagrantc>
"cat | base64" wouldn't log the password in bash history :)
18:51
<alkisg>
Heh, it'll be in ltsp.conf though :D
18:52
<vagrantc>
:)
18:52
<alkisg>
Hrm although this doesn't allow schools to define a single password for all users and completely omit the usernames from lts.conf
18:53
<vagrantc>
pattern-matching? e.g. guest*:
18:53
<alkisg>
OK that could be an additional directive, one to derive the password from the username
18:54
Patterns might be good too
18:54
<vagrantc>
the available users are all known, yes?
18:54
at least during boot
18:58
<alkisg>
yes
18:59
<vagrantc>
could you also disable users with user:! or user:x
19:07
<alkisg>
i have a regex to omit them
19:35emOne has joined IRC (emOne!~emOne@unaffiliated/emone)
20:03* alkisg will probably end up implementing HOST_TO_USERNAME and USERNAME_TO_PASS regexes...
20:03
<alkisg>
The first would be to map pc01 to user01, and the second to map user01 to pass01 or staticpass
20:04
(and the username will be used for autologin, that is)
20:23
<Hyperbyte>
alkisg, thanks... who knows. :-)
20:24
Can you point me to some recent/up-to-date information about NBD swap with LTSP and remote syslog? This is for chrootless LTSP with Ubuntu 18. I have some brand new Intel NUC clients that are randomly freezing. I think it's because they're running out of RAM possibly.
20:25
<alkisg>
It's on by default, you shouldn't need to do anything to enable it
20:25
Run `free` on the client and see
20:25
Although, I've heard of freezes *because* of nbd swap, so I want to do a lot of tests before importing it to ltsp19+
20:26
Whenever possible, clients should have local swap, it's much more efficient and doesn't bother the network/server when the client needs it
20:30
(e.g. if 3 clients are out of ram and use swap, the rest e.g. 10 clients and the server also can't work anymore because of the 3 clients swap activity)
20:42
Maybe nowadays the best would be: zram when there's no swap at all, and zswap when there's also nbd swap. And no z* involved when there's local swap.
20:46Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
20:46
<quinox>
remote rsyslog can lock machines up if it isn't allowed to write overflowing buffers to a drive or drop messages
20:47
that was one of the nastier problems I had to debug
20:48
<||cw>
if you're actually using swap, your PCs are underspec'd for the workload. allocating heaps to swap is fine, just actually needed to move data in an out is trouble. less of an issue on a local disk, but it's still trouble just because of how fast cpu and ram have out paced HDD performance
20:58ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
21:04gdi2k has left IRC (gdi2k!~gdi2k@180.190.170.240, Read error: Connection reset by peer)
21:33kjackal has joined IRC (kjackal!~quassel@ppp-94-66-220-142.home.otenet.gr)
22:21kjackal has left IRC (kjackal!~quassel@ppp-94-66-220-142.home.otenet.gr, Ping timeout: 248 seconds)
23:57vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)