02:25 | gdi2k has left IRC (gdi2k!~gdi2k@58.69.160.28, Read error: Connection reset by peer) | |
02:26 | gdi2k has joined IRC (gdi2k!~gdi2k@58.69.160.28) | |
02:32 | map7 has joined IRC (map7!~user@103.232.216.31) | |
02:53 | <map7> Could I use Samba to mount /home on fat-clients (LTSP 20.3) instead of SSHFS/NFS?
| |
02:57 | <vagrantc> yes
| |
02:57 | probably
| |
02:57 | :)
| |
02:58 | <map7> What about using NFSv4 instead of NFSv3?
| |
02:59 | I think the default for the current ltsp 20.3 is to mount using NFSv3 in Debian 10
| |
03:00 | Just wondering if anyone has tried NFSv4 with LTSP or am I going down a rabbit hole here?
| |
03:00 | <vagrantc> i think it requires a working kerberos implementation or something
| |
03:01 | if so, definitely serious rabbit hole adventures
| |
03:02 | <map7> hmmm, ok thanks for the heads up
| |
03:04 | I need coffee before looking at this!
| |
03:54 | vagrantc: kerberos is optional
| |
04:02 | <vagrantc> what would you get with nfsv4 that isn't in nfsv3?
| |
04:03 | <map7> I believe it would be faster
| |
04:03 | https://www.quora.com/What-is-the-difference-between-NFSv3-and-NFSv4
| |
04:03 | <vagrantc> the main feature i've ever heard was authentication and encryption through kerberos
| |
04:03 | <map7> It has parallel high bandwidth access
| |
04:03 | Multiple operations per RPC
| |
04:04 | I'm just testing if this is true in a real world example
| |
04:04 | I'll let you know the results
| |
04:05 | Maybe I'll start a performance page on the ltsp wiki
| |
04:05 | what do you think?
| |
04:05 | <vagrantc> go for it :)
| |
05:13 | <alkisg> I've tested and troubleshooted nfs performance, and I found a very serious bug that affected it since 10+ years, and I managed to get the kernel maintainers to fix it, and I put a workaround in LTSP code until the fix reaches distributions
| |
05:14 | Apart from that, I'm getting full network bandwidth utilization, so I don't think there's much room from improvement, either on nfs3 or 4
| |
05:15 | <map7> alkisg: Fair enough. From my tests of NFSv4 and different rsize & wsize and came to the same conclusion
| |
05:15 | alkisg: Have you tried samba?
| |
05:15 | for mounting /home
| |
05:15 | <alkisg> Without the bug fix, rsize and wsize can affect performance. With the bug fix, it's best to leave them to their default 1M sizes
| |
05:16 | No, I haven't tried samba
| |
05:16 | Since I'm already getting 1 gbps with minimum cpu usage, I don't think it can be optimized by something else
| |
05:17 | sshfs also gives 1 gbps, but wastes cpu and has some issues with file locks, so that one can be optimized, sure
| |
05:17 | but it's the default as it's secure
| |
05:17 | <map7> I'm more worried about lots of little files and random reads
| |
05:17 | I found a big difference in speed with NFSv3/4 & SSHFS, SSHFS was twice as slow in my test
| |
05:17 | <alkisg> NFS is better there as it's a kernel module, so it can finetune whatever it needs from file system cache
| |
05:18 | While sshfs is userspace, based on fuse
| |
05:18 | I think samba is userspace too, not sure
| |
05:18 | IF it applies you to, you may also try "loopback files as home dirs"
| |
05:19 | And then have ext4 inside the loopback file
| |
05:19 | systemd-homed is moving towards that direction, mainly for the encryption though
| |
05:21 | <map7> Ok cool. First I'll check out samba and see what the performance is like there
| |
05:53 | <alkisg> vagrantc: yey, I got upload rights in Ubuntu for ltsp/epoptes :)
| |
06:38 | <vagrantc> alkisg: yay!
| |
06:39 | alkisg: does that mean you can also schedule sync requests from debian?
| |
06:41 | * vagrantc postpones till later | |
06:41 | * vagrantc waves | |
06:41 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
06:49 | <alkisg> Yup, it does :)
| |
06:59 | adrianor1 has joined IRC (adrianor1!~adrianorg@189.114.158.91) | |
07:02 | adrianorg has left IRC (adrianorg!~adrianorg@179.187.26.41.dynamic.adsl.gvt.net.br, Ping timeout: 240 seconds) | |
07:18 | NecTal has joined IRC (NecTal!c27e6a95@194.126.106.149) | |
07:20 | <NecTal> Hello. Can someone tell me why isn't dns hostnames available in thin client? As in i have separate dns server. All hostnames are working in ltsp server but not in thinclient.
| |
07:21 | <alkisg> Does the thin client have the correct dns server and search domain?
| |
07:22 | Compare systemd-resolve --status in server and clients
| |
07:24 | <NecTal> Server and client both have dns server in global section.
| |
07:25 | <alkisg> Tell me a DNS command that returns a different result on the server vs the client
| |
07:25 | E.g.: host mypc
| |
07:26 | <NecTal> When i try to ping some server in my network. In server i can ping like ping msfile. But in client i cannot ping.
| |
07:26 | <alkisg> Use the host command, not ping
| |
07:26 | And tell me the exact output
| |
07:27 | <NecTal> In server host msfile
| |
07:27 | msfile.ms.trafo.ee has address 172.16.1.201
| |
07:27 | And in client
| |
07:27 | Host msfile not found: 2(SERVFAIL)
| |
07:27 | <alkisg> Now in client try: host msfile.ms.trafo.ee
| |
07:28 | <NecTal> Like that it works.
| |
07:28 | <alkisg> (09:21:52 AM) alkisg: Does the thin client have the correct dns server and search domain? ==>
| |
07:28 | so I assume no search domai
| |
07:28 | (09:22:12 AM) alkisg: Compare systemd-resolve --status in server and clients => check search domain there
| |
07:28 | <NecTal> Yeah. Seems like search domain is missing. Where can i define that? ltsp.conf?
| |
07:29 | <alkisg> Normally, in your dhcp server
| |
07:29 | How do your clients get IP, and how does the server get IP?
| |
07:29 | <NecTal> Client gets ip with dnsmasq from ltsp server.
| |
07:29 | <alkisg> 2-nic setup?
| |
07:29 | <NecTal> Yes.
| |
07:29 | <alkisg> Then you need to put searchdomain in dnsmasq
| |
07:30 | I don't know the syntax off-hand, but it should be in the man page
| |
07:30 | <NecTal> Okay. I will take a look.
| |
07:30 | Thank you for your help.
| |
07:30 | <alkisg> np
| |
07:32 | Quick googling says either #domain=thekelleys.org.uk or dhcp-option-force=option:domain-search,internal,maindomain.com
| |
07:45 | NecTal: you might also want to file a bug report in ltsp for this, it would probably be worth it to add it as an example to the default dnsmasq.conf
| |
07:45 | !bug
| |
07:45 | <ltspbot> bug: To file a bug report for upstream LTSP, go to https://github.com/ltsp/ltsp/issues
| |
07:46 | woernie has joined IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de) | |
08:06 | quinox has left IRC (quinox!~quinox@ghost.qtea.nl, *.net *.split) | |
08:07 | quinox has joined IRC (quinox!~quinox@ghost.qtea.nl) | |
08:49 | woernie has left IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de, Ping timeout: 256 seconds) | |
08:50 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
08:56 | shored has left IRC (shored!~shored@87-92-92-55.bb.dnainternet.fi, Read error: Connection reset by peer) | |
08:57 | shored has joined IRC (shored!~shored@87-92-92-55.bb.dnainternet.fi) | |
09:12 | NecTal has left IRC (NecTal!c27e6a95@194.126.106.149, Ping timeout: 240 seconds) | |
11:25 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 250 seconds) | |
11:31 | Teridon has joined IRC (Teridon!~Teridon@dragon.teridon.com) | |
11:33 | woernie has joined IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de) | |
11:35 | Teridon has left IRC (Teridon!~Teridon@dragon.teridon.com, Ping timeout: 240 seconds) | |
11:37 | woernie has left IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de, Ping timeout: 250 seconds) | |
11:57 | woernie has joined IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de) | |
14:12 | Teridon has joined IRC (Teridon!~Teridon@dragon.teridon.com) | |
14:13 | Teridon has left IRC (Teridon!~Teridon@dragon.teridon.com, Client Quit) | |
14:22 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
14:28 | ltspbot` has joined IRC (ltspbot`!~supybot@devs.ts.sch.gr) | |
14:28 | ltspbot has left IRC (ltspbot!~supybot@devs.ts.sch.gr, Ping timeout: 240 seconds) | |
14:32 | <alkisg> vagrantc: yup, syncing with debian is also included
| |
14:32 | Btw, epoptes has a problem with the new socat, due to a bug in socat,
| |
14:33 | which is fixed in the new bug-fixing upstream socat version,
| |
14:33 | I wonder if it would be easy to ask the debian maintainer to package that new bug fixing version...
| |
14:34 | Specifically, right click on client, open terminal, root locally => the arrow keys etc don't work in that terminal
| |
14:42 | <vagrantc> weird
| |
14:42 | alkisg: doesn't hurt to ask :)
| |
14:42 | alkisg: you could submit a normal bug and mark that it "affects" epoptes
| |
14:43 | <alkisg> Gotcha. I'm waiting for a second feedback from the socat developer; I'll file the bug report after I get it
| |
14:43 | I've no idea how to tag "affects" on the debian bug tracker, but I guess I'll find it
| |
14:49 | <vagrantc> https://www.debian.org/Bugs/server-control#affects
| |
14:49 | include the line "Control: affects -1 epoptes" in your submission email
| |
16:13 | Klimm has joined IRC (Klimm!~Georg@p54897887.dip0.t-ipconnect.de) | |
16:16 | statler has left IRC (statler!~Georg@p54897635.dip0.t-ipconnect.de, Ping timeout: 256 seconds) | |
16:36 | mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Remote host closed the connection) | |
16:43 | mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy) | |
17:06 | markit has joined IRC (markit!~marco@mail.ammdomus.it) | |
18:35 | ltspbot has joined IRC (ltspbot!~supybot@devs.ts.sch.gr) | |
18:56 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
19:13 | woernie has left IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de, Ping timeout: 258 seconds) | |
19:15 | woernie has joined IRC (woernie!~werner@p508673F2.dip0.t-ipconnect.de) | |
19:16 | GodFather has joined IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com) | |
19:26 | ArcticWolfen has joined IRC (ArcticWolfen!bc729916@188.114.153.22) | |
19:26 | woernie has left IRC (woernie!~werner@p508673F2.dip0.t-ipconnect.de, Read error: Connection reset by peer) | |
19:30 | woernie has joined IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de) | |
19:32 | <ArcticWolfen> Hi, I'm trying to install LTSP on Debian buster running on a Pine64. I can't download the LTSP:PPA, this link does not work for me https://ltsp.org/misc/ltsp-ubuntu-ppa-focal.list
| |
19:39 | ArcticWolfen has left IRC (ArcticWolfen!bc729916@188.114.153.22, Remote host closed the connection) | |
19:43 | ArcticWolfen has joined IRC (ArcticWolfen!bc729916@188.114.153.22) | |
19:44 | <alkisg> ArcticWolfen: whoops, please put bionic instead of focal and I'll fix it tomorrow
| |
19:44 | it's the same for now
| |
19:44 | <ArcticWolfen> thanks
| |
19:49 | That did it installing now
| |
19:52 | <alkisg> ArcticWolfen: I managed to omit them in the last push; I fixed it now; it should appear online in a minute
| |
20:28 | Klimm has left IRC (Klimm!~Georg@p54897887.dip0.t-ipconnect.de, Remote host closed the connection) | |
20:57 | ArcticWolfen has left IRC (ArcticWolfen!bc729916@188.114.153.22, Remote host closed the connection) | |
21:19 | markit has left IRC (markit!~marco@mail.ammdomus.it, ) | |
21:38 | <bluejaypop> hello people, I'm looking for a solution for ltsp for example in different city.
| |
21:39 | shored has left IRC (shored!~shored@87-92-92-55.bb.dnainternet.fi, Read error: Connection reset by peer) | |
21:40 | shored has joined IRC (shored!~shored@87-92-92-55.bb.dnainternet.fi) | |
21:46 | woernie has left IRC (woernie!~werner@p5DDEC5BE.dip0.t-ipconnect.de, Ping timeout: 260 seconds) | |
23:46 | GodFather has left IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com, Ping timeout: 250 seconds) | |