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


Channel log from 11 June 2020   (all times are UTC)

03:40vsuojanen has joined IRC (vsuojanen!~vsuojanen@cable-hml-58568f-194.dhcp.inet.fi)
03:45vsuojanen has left IRC (vsuojanen!~vsuojanen@cable-hml-58568f-194.dhcp.inet.fi, Ping timeout: 260 seconds)
04:36quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 2.8)
04:39quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
07:32woernie has joined IRC (woernie!~werner@p5ddecf52.dip0.t-ipconnect.de)
11:17vsuojanen has joined IRC (vsuojanen!~vsuojanen@cable-hml-58568f-194.dhcp.inet.fi)
11:21vsuojanen has left IRC (vsuojanen!~vsuojanen@cable-hml-58568f-194.dhcp.inet.fi, Ping timeout: 240 seconds)
12:16woernie has left IRC (woernie!~werner@p5ddecf52.dip0.t-ipconnect.de, Ping timeout: 246 seconds)
12:19woernie has joined IRC (woernie!~werner@p5ddecf52.dip0.t-ipconnect.de)
13:50markit has joined IRC (markit!~marco@mail.ammdomus.it)
13:52
<markit>
hi alkisg :) by chance, do you "support", suggest and have you a good experience with ZFS on ltsp server? The only feature I really would love is "rolling snapshots" (i.e. "n" sets of last snapshot), just in case someone deletes by mistake something important /tons of
14:06
<alkisg>
Hi markit, I have no experience with ZFS but I'm hearing good things about it; regarding LTSP, I don't expect it to take any impact, it should just work
14:08
<markit>
I'm testing it in Proxmox, but seems that read performance is not that stellar without tuning
14:08
also I've consumer grade ssd that could weare out "fast" (but realistically, how many hours will be on that server I'm trying to upgrade?)
14:10
<alkisg>
It's best if /home is on SSD. There too, I don't have a lot of experience, as most schools had HDDs
14:10
Root /, can be on HDD or slow ZFS or whatever without much impact to the clients, as it's cached in RAM anyway
14:11
<markit>
I've read in the channel log that you are very busy until Agust, then LTSP will improve/evolve/bring new stuff again... looking forward it :) Also "multiseat"? Cool stuff (I've no pratical use myself, but always been fascinated by it)
14:12
<highvoltage>
I ran LTSP (old LTSP 5 series) on ZFS for an office with about 40 desktops before
14:12
(storage on 4x HDD + 2x SSD as cache) and it ran quite well
14:12
<markit>
highvoltage: I've a single Crucial 500GB sata ssh :)
14:15
<highvoltage>
on my personal machines at home I use single SSDs for cache and performance is still great (as in, significantly better as any kind of HDD configuration without a cache backup)
14:17
<markit>
highvoltage: I'm afraid of write wearout of consumer grade ssd
14:17
<highvoltage>
as long as you can replace it at some point that's fine
14:17
you don't lose data when you lose your cache
14:18
I work a variety of SSDs quite hard and haven't had one fail in ages
14:18
<markit>
highvoltage: sure, I mean me that have only one ssd, not as cache, but as "the one the only one" disk
14:18
<highvoltage>
markit: oh yeah, that would be bad :)
14:19
in zfs you can use your usual disks in mirror and add the SSD as cache (then when it reads data from the disks, it also goes to the SSD, and future reads happen from there, also drastically speeding up writes to your main disks)
14:19
that's my usual minimum setup when it comes to zfs
14:21
<markit>
highvoltage: I'm configuring my new proxmox server with ZFS, it's really cool
14:21* markit just reading that Kubuntu has no installer with ZFS option, should install ubuntu server then add kde packages... too much work, amybe for 22.04 :)
15:41
<markit>
alkisg: I'm still confused by the "server" name of ltsp. My server name is kub2040, do I have to put also "server" in /etc/hosts? I see it in nfs home config so I think clients have to resolve it to 192.168.67.1 and not my "wan" IP
15:41
or it's automagically done by ltsp scripts? Any config to bind "server" to "client interface ip"?
16:25hark has left IRC (hark!~hark@yavin.puscii.nl)
17:05
<alkisg>
markit: the server name, "server", is automagically done by ltsp scripts
17:05
No matter what the server actual name is
17:05
This is needed for many things, e.g. for the SSH keys to work even if the server IP or hostname change
17:06
So an entry for "server" will always exist in the client's /etc/hosts
17:07
<markit>
alkisg: thanks a lot :) Is this true also if I've a "one nic" config?
17:09
<alkisg>
Yes
17:15
<markit>
(btw, I'm "migrating" from 16.04 - 32 to 20.04 - 64 bit (reinstalling and then importing accounts and so on), doing the work in a VM (so I can snapshot often) and then creating (qemu-img convert -f qcow2 -O raw my-qcow2.img /dev/sdb) to the ssd of the school's server. Is very time consuming, let's hope everything will work)
18:05lucascastro has joined IRC (lucascastro!~lucascast@177-185-139-41.isotelco.net.br)
18:06dsj2 has joined IRC (dsj2!~dsj2222@70-237-72-173.lightspeed.chrlnc.sbcglobal.net)
20:44mgariepy_ has joined IRC (mgariepy_!~mgariepy@styx-204.ccs.usherbrooke.ca)
20:44mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Ping timeout: 264 seconds)
20:47mgariepy_ has left IRC (mgariepy_!~mgariepy@styx-204.ccs.usherbrooke.ca, Client Quit)
20:48mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)
21:44woernie has left IRC (woernie!~werner@p5ddecf52.dip0.t-ipconnect.de, Remote host closed the connection)
23:26adrianorg has joined IRC (adrianorg!~adrianorg@186.213.156.235)
23:28adrianor1 has left IRC (adrianor1!~adrianorg@177.156.59.180, Ping timeout: 256 seconds)