|02:33||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)|
|03:06||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Ping timeout: 240 seconds)|
|03:42||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)|
|04:36||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving)|
|05:58||quinox has left IRC (firstname.lastname@example.org, Quit: WeeChat 3.4)|
|06:01||quinox has joined IRC (email@example.com)|
|06:07||Hyperbyte has left IRC (Hyperbytefirstname.lastname@example.org, *.net *.split)|
|06:12||Hyperbyte has joined IRC (Hyperbyteemail@example.com)|
|06:31||woernie has joined IRC (firstname.lastname@example.org)|
|06:42||spectra has left IRC (email@example.com, Quit: ZNC - http://znc.sourceforge.net)|
|07:24||woernie has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
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)
re: rockpro64 ltsp+pxe booting
Would I pull intrid or something?
sfxworks: you need the kernel and initrd, yes
But I've no idea about uboot, so I can't provide details :/
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
Otherwise, try to find vagrantc , he might have some experience in the matter
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
a later build* specifically,
I might just do a two nic system real quick to replicate his setup...
|07:59||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
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
The epoptes daemon keeps communicating with the clients, so it knows when they go offline
If you're up to it, you may even make a more generic "epoptes-cli" command out of it :)
|09:19||woernie has joined IRC (email@example.com)|
|09:39||woernie has left IRC (firstname.lastname@example.org, Ping timeout: 250 seconds)|
|10:15||woernie has joined IRC (email@example.com)|
|10:19||woernie has left IRC (firstname.lastname@example.org, Ping timeout: 250 seconds)|
|11:51||danboid has joined IRC (email@example.com)|
Happy Friday LTSPers!
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
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.
I've posted this problem to the nslcd mailig list but no response yet
|11:59||Faith has joined IRC (Faith!~Faith@user/faith)|
If anyone here can spot anything in there that looks off then I'll love you forever!
danboid, are you sure it's not a hostname resolution problem?
Your LTSP server or clients may be using nameservers that don't properly resolve the internal hostnames.
Hyperbyte, I've almost fixed it
The delay is only whe using SSH keys
Hmm. 14 second login whe using a key isn't almost fixed
Its fine when I disabled keys and just use passwords, after I rebooted
ssh had this problem:
systemd: ssh.service: Found left-over process 1835582 (bash) in control group while starting unit.
Which was solved by a reboot and I think I've found a fix for that here
|13:58||Nils[m]1234 has joined IRC (Nils[m]1234!~ravagexen@2001:470:69fc:105::1:5087)|
|15:54||woernie has joined IRC (firstname.lastname@example.org)|
|16:25||ltspbot has joined IRC (email@example.com)|