IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 3 August 2020 (all times are UTC)
| 01:27 | GodFather has joined IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com) | |
| 03:07 | GodFather has left IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com, Ping timeout: 264 seconds) | |
| 05:36 | woernie has left IRC (woernie!~werner@p5dded9eb.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 07:04 | RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro) | |
| 08:18 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
| 08:51 | adrianor1 has joined IRC (adrianor1!~adrianorg@177.204.157.230.dynamic.adsl.gvt.net.br) | |
| 08:55 | adrianorg has left IRC (adrianorg!~adrianorg@201.22.230.1, Ping timeout: 256 seconds) | |
| 10:12 | danboid has joined IRC (danboid!~ISDADS\sg@cpc126962-macc4-2-0-cust227.1-3.cable.virginm.net) | |
| 10:13 | <danboid> epoptes can only have one machine as the admin but can multiple users on that machine both use epoptes simultaneously, if they are members of the epoptes group?
| |
| 10:14 | s/both/all
| |
| 10:14 | or is it designed to only be used by one admin user
| |
| 10:18 | <alkisg> danboid: multiple users are supported
| |
| 10:18 | And you can use ssh -X to launch it from other computers
| |
| 10:20 | <danboid> OK that's good to know
| |
| 12:08 | pw77 has joined IRC (pw77!a7152a14@167.21.42.20) | |
| 12:43 | GodFather has joined IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com) | |
| 12:43 | GodFather has left IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com, Remote host closed the connection) | |
| 12:45 | GodFather has joined IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com) | |
| 12:59 | danboid has left IRC (danboid!~ISDADS\sg@cpc126962-macc4-2-0-cust227.1-3.cable.virginm.net, Quit: Leaving) | |
| 13:54 | vsuojanen has left IRC (vsuojanen!~vsuojanen@cable-hml-58568f-194.dhcp.inet.fi, Ping timeout: 240 seconds) | |
| 13:56 | vsuojanen has joined IRC (vsuojanen!~vsuojanen@cable-hml-58568f-194.dhcp.inet.fi) | |
| 14:08 | pw77 has left IRC (pw77!a7152a14@167.21.42.20, Ping timeout: 245 seconds) | |
| 14:52 | mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Ping timeout: 256 seconds) | |
| 14:52 | mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy) | |
| 15:15 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 240 seconds) | |
| 16:19 | pw77 has joined IRC (pw77!a7152a14@167.21.42.20) | |
| 16:22 | <pw77> Howdy Everyone. I think the performance issues with LTSP5 machines has been corrected. I added the two lines from alkisg to lts.conf and the machines work fine. I'm still seeing very slow boot times for some machines that worked fine under Ubuntu 16.04 LTSP5 (non-Greek-PPA). They take several minutes sitting at "Loading
| |
| 16:22 | initrd.img-5.4.0-42-generic". These machines have gig nics and reach close to that bandwidth when I'm able to get to a console to test it. )
| |
| 16:36 | <alkisg> pw77: try to remove quiet splash in order to see in which point the clients delay
| |
| 16:36 | !quiet
| |
| 16:36 | <ltspbot> quiet: to enable the Debian kernel and initramfs to show up more messages, in order to better troubleshoot the boot process, remove "quiet" from /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
| |
| 16:37 | pw77 has left IRC (pw77!a7152a14@167.21.42.20, Remote host closed the connection) | |
| 16:41 | adrianor1 has left IRC (adrianor1!~adrianorg@177.204.157.230.dynamic.adsl.gvt.net.br, Quit: leaving) | |
| 16:47 | pw77 has joined IRC (pw77!a7152a14@167.21.42.20) | |
| 16:52 | <pw77> I looked in /var//lib/tftpboot/ltsp/amd64/pxelinux.cfg/default but didn't find any instance of 'quiet'. I should have been more clear, these are amd64 machines
| |
| 17:08 | <alkisg> pw77: if they're really taking time at "loading initrd", that's related to tftp speed
| |
| 17:08 | Which in turn is related to the ipxe or pxe stack or tftp server (dnsmasq?) version
| |
| 17:08 | There's no ltsp code involved there
| |
| 17:09 | <pw77> Ok.
| |
| 17:15 | Thanks for the help so far. I think I have enough to do some more testing. I appreciate the help!
| |
| 17:28 | <quinox> possibly unrelated, but I have 1 machine that boots incredibly slowly unless I configure a small MTU. Shoddy firmware or something
| |
| 17:35 | and it was nothing outrageous, 1500 was too much, 900 was fine
| |
| 17:48 | pw77 has left IRC (pw77!a7152a14@167.21.42.20, Remote host closed the connection) | |
| 17:49 | pw77 has joined IRC (pw77!a7152a14@167.21.42.20) | |
| 17:50 | <pw77> quinox Where is that MTU specified?
| |
| 17:55 | <quinox> I did it in my DHCP server
| |
| 18:01 | <pw77> Gotcha
| |
| 18:04 | adrianorg has joined IRC (adrianorg!~adrianorg@177.204.157.230.dynamic.adsl.gvt.net.br) | |
| 18:08 | <pw77> That appeared to speed up the issue with initrd
| |
| 18:09 | lucascastro has left IRC (lucascastro!~lucascast@177-185-139-222.dynamic.isotelco.net.br, Remote host closed the connection) | |
| 18:09 | lucascastro has joined IRC (lucascastro!~lucascast@177-185-139-222.dynamic.isotelco.net.br) | |
| 18:42 | pw77 has left IRC (pw77!a7152a14@167.21.42.20, Ping timeout: 245 seconds) | |
| 19:13 | sutula has left IRC (sutula!~sutula@184.97.13.190, Ping timeout: 264 seconds) | |
| 19:15 | sutula has joined IRC (sutula!~sutula@184.97.13.190) | |
| 19:20 | sutula has left IRC (sutula!~sutula@184.97.13.190, Read error: Connection reset by peer) | |
| 19:20 | sutula has joined IRC (sutula!~sutula@184.97.13.190) | |
| 19:24 | RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.) | |
| 20:42 | GodFather has left IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com, Ping timeout: 240 seconds) | |
| 20:48 | sutula has left IRC (sutula!~sutula@184.97.13.190, Read error: Connection reset by peer) | |
| 20:48 | sutula has joined IRC (sutula!~sutula@184.97.13.190) | |
| 22:20 | lucas_ has joined IRC (lucas_!~lucascast@186.193.183.161.jupiter.com.br) | |
| 22:23 | lucascastro has left IRC (lucascastro!~lucascast@177-185-139-222.dynamic.isotelco.net.br, Ping timeout: 265 seconds) | |