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


Channel log from 28 January 2022   (all times are UTC)

02:33vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)
03:06vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Ping timeout: 240 seconds)
03:42vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)
04:36vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving)
05:58quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 3.4)
06:01quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
06:07Hyperbyte has left IRC (Hyperbyte!~jan@middelkoop.cc, *.net *.split)
06:12Hyperbyte has joined IRC (Hyperbyte!~jan@middelkoop.cc)
06:31woernie has joined IRC (woernie!~werner@p5b296cc2.dip0.t-ipconnect.de)
06:42spectra has left IRC (spectra!~spectra@63.142.251.150, Quit: ZNC - http://znc.sourceforge.net)
07:24woernie has left IRC (woernie!~werner@p5b296cc2.dip0.t-ipconnect.de, Remote host closed the connection)
07:47
<sfxworks[m]>
So I can use the nfs command but im assuming I don't want to pull the actual image....... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/8ad22fe1637e04c37862ae8aa13945c6b812cbb4)
07:47
re: rockpro64 ltsp+pxe booting
07:48
Would I pull intrid or something?
07:49
<alkisg>
sfxworks: you need the kernel and initrd, yes
07:50
But I've no idea about uboot, so I can't provide details :/
07:51
It's probably better to search the net for rockpro64 pxe booting first, and AFTER you found how to do it in general, then I might be able to help you fill the missing bits for LTSP
07:52
Otherwise, try to find vagrantc , he might have some experience in the matter
07:53
<sfxworks[m]>
My friend was able to pxe boot with the setup here https://forum.pine64.org/showthread.php?tid=6814 and flashed the spi for me. I tried flashing the spi with the later build and succeeded but it didn't follow the tftp server addr
07:53
a later build* specifically,
07:54
https://github.com/sigmaris/u-boot/releases
07:54
I might just do a two nic system real quick to replicate his setup...
07:59ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
08:54
<alkisg>
Hi dfanp, currently epoptes isn't scriptable, so you'd need to write a python-twisted program to directly access the epoptes daemon, which isn't trivial
08:55
The epoptes daemon keeps communicating with the clients, so it knows when they go offline
08:59
If you're up to it, you may even make a more generic "epoptes-cli" command out of it :)
09:19woernie has joined IRC (woernie!~werner@p200300cf0714320004f145cbfb748e7a.dip0.t-ipconnect.de)
09:39woernie has left IRC (woernie!~werner@p200300cf0714320004f145cbfb748e7a.dip0.t-ipconnect.de, Ping timeout: 250 seconds)
10:15woernie has joined IRC (woernie!~werner@p200300cf0714320004f145cbfb748e7a.dip0.t-ipconnect.de)
10:19woernie has left IRC (woernie!~werner@p200300cf0714320004f145cbfb748e7a.dip0.t-ipconnect.de, Ping timeout: 250 seconds)
11:51danboid has joined IRC (danboid!~dan@portal.salford.ac.uk)
11:51
<danboid>
Happy Friday LTSPers!
11:54
alkisg, OK so I think this is my final LTSP hurdle, I'm SURE! With just ssh, logins are instant. Just LDAP, logins are snappy. ssh + LDAP = 20+ second delay on ssh logins. Have you seen this before? The internet hasn't, according to my searches. I've done all the ssh server tweaks a man can
11:56
I've tried disabling ssh keys and all sorts. As soon as I disable nslcd, ssh logins are instant so its a LDAP and or PAM thing but the logs aren't helping me much.
11:57
I've posted this problem to the nslcd mailig list but no response yet
11:59
https://lists.arthurdejong.org/nss-pam-ldapd-users/2022/msg00010.html
11:59Faith has joined IRC (Faith!~Faith@user/faith)
12:00
<danboid>
If anyone here can spot anything in there that looks off then I'll love you forever!
12:55
<Hyperbyte>
danboid, are you sure it's not a hostname resolution problem?
12:56
Your LTSP server or clients may be using nameservers that don't properly resolve the internal hostnames.
12:56
<danboid>
Hyperbyte, I've almost fixed it
12:56
The delay is only whe using SSH keys
13:00
Hmm. 14 second login whe using a key isn't almost fixed
13:01
Its fine when I disabled keys and just use passwords, after I rebooted
13:01
ssh had this problem:
13:01
systemd[1]: ssh.service: Found left-over process 1835582 (bash) in control group while starting unit.
13:02
Which was solved by a reboot and I think I've found a fix for that here
13:02
https://serverfault.com/questions/967325/sshd-starts-two-processes-but-systemd-stops-only-one
13:58Nils[m]1234 has joined IRC (Nils[m]1234!~ravagexen@2001:470:69fc:105::1:5087)
15:54woernie has joined IRC (woernie!~werner@p5b296cc2.dip0.t-ipconnect.de)
16:25ltspbot has joined IRC (ltspbot!~supybot@devs.ts.sch.gr)