04:30 | ltspbot has joined IRC (ltspbot!~supybot@devs.ts.sch.gr) | |
04:50 | ltspbot has joined IRC (ltspbot!~supybot@devs.ts.sch.gr) | |
05:38 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
06:09 | * AllofaSuddenIMis uploaded an image: (46KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/OODipRkdbAjZtmfaYNExPKvo/2022-04-27%2009_08_34.jpg > | |
06:09 | <AllofaSuddenIMis> Thanks for answer. I get this error and couldn't find a way to fix it. tftpd-hpa.service is running, looks like client can't reach it and load the image...
| |
06:16 | <alkisg> All of a Sudden I Miss Everyone: check your tftp server logs, to see which file the clients request, or boot the client using ipxe.iso, so that you see the configuration it receives
| |
06:16 | All of a Sudden I Miss Everyone: if you do have tftpd-hpa, it means you have a linux serer; why not use the default dnsmasq/proxydhcp instead?
| |
06:17 | The less you diverge from the defaults, the less administration work you need to do...
| |
06:18 | I mean, by default ltsp uses dnsmasq for both dhcp and tftp; it doesn't use tftpd-hpa nor isc-dhcpd
| |
06:20 | * AllofaSuddenIMis uploaded an image: (526KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/jqDKOkhckcXGmJAYQQiyYMkl/2022-04-27%2009_19_25.jpg > | |
06:20 | <AllofaSuddenIMis> so i can simply disable tftpd-hpa? don't exacly know how it works so far, sorry. Here is my dnsmasq config, is this correct?
| |
06:20 | <alkisg> If you have dnsmasq installed, you should apt purge tftpd-hpa
| |
06:20 | <AllofaSuddenIMis> okay, it's done
| |
06:21 | <alkisg> Your dnsmasq.conf is fine, it's the typical one that ltsp produces
| |
06:36 | <AllofaSuddenIMis> Hm, that is interesting. Trying to start dnsmasq service and get this error message. That is why client couldn't load tftp i suppose
| |
06:36 | * AllofaSuddenIMis uploaded an image: (222KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/bVPJJRCLJfJEemNvstUebORk/2022-04-27%2009_35_53.jpg > | |
06:37 | <AllofaSuddenIMis> What is that mean?
| |
06:39 | <alkisg> All of a Sudden I Miss Everyone: it probably means that you have another dnsmasq.conf. Did you modify /etc/dnsmasq.conf? Did you add another file in /etc/dnsmasq.d?
| |
06:39 | The /etc/dnsmasq.conf file is supposed to be all comments; the ltsp-dnsmasq.conf is supposed to be managed by ltsp; and if you want, you can create a /etc/dnsmasq.d/local.conf file
| |
10:49 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
10:49 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
12:46 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
12:47 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
13:07 | lucascastro has left IRC (lucascastro!~lucascast@192-140-51-138.static.oncabo.net.br, Remote host closed the connection) | |
13:08 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
13:08 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
13:12 | lucascastro has joined IRC (lucascastro!~lucascast@192-140-51-138.static.oncabo.net.br) | |
13:30 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
14:22 | lucascastro has left IRC (lucascastro!~lucascast@192-140-51-138.static.oncabo.net.br, Read error: Connection reset by peer) | |
14:22 | lucascastro has joined IRC (lucascastro!~lucascast@192-140-51-138.static.oncabo.net.br) | |
14:30 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
15:10 | oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
15:11 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 256 seconds) | |
15:16 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
15:16 | oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 256 seconds) | |
15:58 | oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
15:58 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 272 seconds) | |
16:20 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
16:21 | oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 250 seconds) | |
16:32 | oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
16:33 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 246 seconds) | |
16:45 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
16:46 | oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 276 seconds) | |
17:00 | oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
17:00 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 276 seconds) | |
17:05 | oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 240 seconds) | |
17:05 | oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
17:10 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
17:10 | oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 272 seconds) | |
17:18 | oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
17:18 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 276 seconds) | |
17:30 | oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 246 seconds) | |
17:30 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
17:38 | oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
17:38 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 246 seconds) | |
17:43 | oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 240 seconds) | |
17:43 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
18:12 | oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
18:12 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 240 seconds) | |
18:49 | bobby99 has joined IRC (bobby99!~bobby99@ip-109-192-072-233.um38.pools.vodafone-ip.de) | |
18:49 | <bobby99> Good evening. I have created a new user on the server that does not appear on the client. What did I do wrong?
| |
18:54 | oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 256 seconds) | |
18:54 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
18:58 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 240 seconds) | |
19:11 | bobby99 has left IRC (bobby99!~bobby99@ip-109-192-072-233.um38.pools.vodafone-ip.de, Quit: Client closed) | |
20:07 | bobby99 has joined IRC (bobby99!~bobby99@ip-109-192-072-233.um38.pools.vodafone-ip.de) | |
20:09 | <bobby99> So I found that I need to run "ltsp initrd". I did it, and the new user appears on the client. Howevr, I cannot login on the client any more. No user can. When I try, I can't login on th server any more. I have to delete the .Xauthority file so I can login on the server again.
| |
20:09 | What's wrong?
| |
20:09 | <vagrantc> ouch
| |
20:12 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
20:14 | <bobby99> Hold on...
| |
20:14 | bobby99 has left IRC (bobby99!~bobby99@ip-109-192-072-233.um38.pools.vodafone-ip.de, Quit: Client closed) | |
20:17 | bobby99 has joined IRC (bobby99!~bobby99@ip-109-192-072-233.um38.pools.vodafone-ip.de) | |
20:17 | <bobby99> So, I just resolved it...
| |
20:18 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
20:18 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
20:23 | <vagrantc> bobby99: curious what the issue was
| |
20:25 | <bobby99> I had a bunch of ssh options in the ltsp.conf file. For some reason, these have never become effective - until I ran "ltsp initrd" today to make the new user appear. Something must be wrong with these options.
| |
20:25 | <vagrantc> ah
| |
20:25 | that could certainly do that
| |
20:25 | <bobby99> I'm still checking them. I had them in place to make sshfs access faster.
| |
20:26 | SSH_OPTIONS="-o compression=no -o Ciphers=aes128-ctr -o disable_hardlink -o follow_symlinks"
| |
20:26 | Anything wrong with that?
| |
20:28 | <vagrantc> you sure that that compression and cipher actually improves performance? :)
| |
20:29 | <bobby99> No. It was a test based on recommendations from some web sources.
| |
20:29 | Usually, arcfour is the recommended cipher. But for some reason, it didn't work.
| |
20:29 | <vagrantc> it really depends on what you're doing ... compression=yes can often speed things up considerably ... but only if the data you're sending is compressable
| |
20:31 | <bobby99> Seems as if I need some spare time to do more thorough tests...
| |
20:31 | From my current understanding, I only need to run "ltsp initrd" when I change /etc/ltsp/ltsp.conf. Right?
| |
20:32 | <vagrantc> or add users
| |
20:32 | or remove users ...
| |
20:32 | <bobby99> Yes
| |
20:32 | <vagrantc> or install new packages
| |
20:32 | or remove... or upgrade... etc. :)
| |
20:32 | <bobby99> This should be mentioned in a more prominent location on the website.
| |
20:33 | I think it's only in the "Installation" section. Maybe an "Updating" section would be good.
| |
20:34 | That's it for today. Have a good night!
| |
20:34 | bobby99 has left IRC (bobby99!~bobby99@ip-109-192-072-233.um38.pools.vodafone-ip.de, Quit: Client closed) | |