IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 12 April 2023 (all times are UTC)
| 00:19 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50, Quit: leaving) | |
| 05:16 | wyre is back | |
| 05:20 | tru_tru has left IRC (tru_tru!~tru@centos/board/tru, Ping timeout: 276 seconds) | |
| 05:20 | tru_tru has joined IRC (tru_tru!~tru@centos/board/tru) | |
| 05:30 | woernie has joined IRC (woernie!~werner@p5ddec58c.dip0.t-ipconnect.de) | |
| 05:50 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 06:02 | alkisg_irc1 has left IRC (alkisg_irc1!~Thunderbi@2a02:587:7460:3e00:9ea2:f4ff:feb9:a8b0, Remote host closed the connection) | |
| 06:12 | alkisg_irc has joined IRC (alkisg_irc!~Thunderbi@2a02:587:7460:3e00:9ea2:f4ff:feb9:a8b0) | |
| 06:17 | wyre is now away: Auto away at Wed Apr 12 06:14:57 2023 UTC | |
| 06:46 | wyre is back | |
| 07:17 | Vercas696 has joined IRC (Vercas696!~Vercas@gateway/tor-sasl/vercas) | |
| 07:17 | Vercas69 has left IRC (Vercas69!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 07:17 | Vercas696 is now known as Vercas69 | |
| 07:43 | bengoa has left IRC (bengoa!~root@uk.bengoa.org, *.net *.split) | |
| 07:47 | bengoa has joined IRC (bengoa!~root@uk.bengoa.org) | |
| 09:07 | woernie has left IRC (woernie!~werner@p5ddec58c.dip0.t-ipconnect.de, Ping timeout: 265 seconds) | |
| 09:07 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
| 09:18 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 256 seconds) | |
| 09:18 | woernie has joined IRC (woernie!~werner@p5ddec58c.dip0.t-ipconnect.de) | |
| 09:51 | woernie has left IRC (woernie!~werner@p5ddec58c.dip0.t-ipconnect.de, Ping timeout: 276 seconds) | |
| 09:51 | woernie has joined IRC (woernie!~werner@www.velometrik.eu) | |
| 11:16 | fiesh has left IRC (fiesh!~fiesh@2003:fb:1018::21, Quit: [TLS] Client upgrade) | |
| 11:16 | fiesh has joined IRC (fiesh!~fiesh@2003:fb:1018::21) | |
| 11:24 | Vercas69 has left IRC (Vercas69!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
| 11:25 | Vercas69 has joined IRC (Vercas69!~Vercas@gateway/tor-sasl/vercas) | |
| 11:37 | woernie has left IRC (woernie!~werner@www.velometrik.eu, Ping timeout: 240 seconds) | |
| 11:38 | woernie has joined IRC (woernie!~werner@p5ddec58c.dip0.t-ipconnect.de) | |
| 12:13 | woernie has left IRC (woernie!~werner@p5ddec58c.dip0.t-ipconnect.de, Ping timeout: 250 seconds) | |
| 12:13 | woernie has joined IRC (woernie!~werner@www.velometrik.eu) | |
| 12:48 | tomahock[m] has joined IRC (tomahock[m]!~tomahockm@2001:470:69fc:105::3:439f) | |
| 12:49 | Tomahock has joined IRC (Tomahock!~Tomahock@190.119.163.98) | |
| 13:22 | <Tomahock> hello, how to avoid that the user accounts that were used from the clients to access the LTSP on Ubuntu 18, once their desktop is loaded, cannot open a terminal from where they can execute commands
| |
| 13:31 | <quinox> uninstall the terminal? :)
| |
| 13:32 | run some program in "kiosk mode" ?
| |
| 13:33 | they can only destroy their own files, as soon as you reboot an LTSP client it's in a pristine state. What do you want to achieve / prevent?
| |
| 13:50 | <Tomahock> just that they can damage the server if they are expert users in linux commands, then there is no risk that they can access the terminal
| |
| 13:56 | <quinox> if you don't give them root / sudo there's not much they can do to damage anything
| |
| 13:57 | all programs run locally, so if they run a forkbomb they'll only lock up their own computer, not the server
| |
| 13:58 | if they log in on the server using the user accounts to run a forkbomb there... removing the terminal won't help: they can simply connect their laptop to your network to login on the server
| |
| 14:00 | for a professional environment I wouldn't worry about it
| |
| 14:01 | in a school environment with kids: yeah
| |
| 14:02 | there are so many ways to cause havoc
| |
| 14:02 | <Tomahock> Thanks, I wanted to understand that point, so what is loaded in the client is like a sandbox
| |
| 14:02 | In my case, it is for use by university students and some are from systems engineering, some of which are very curious, that's why my query
| |
| 14:03 | <quinox> yes, LTSP runs so called fat clients meaning the files come from the network but the computations are all done locally
| |
| 14:04 | do by default they'll only annoy themselves with their curiosity
| |
| 14:06 | <Tomahock> well thank you very much
| |
| 15:24 | wyre is now away: Auto away at Wed Apr 12 15:22:54 2023 UTC | |
| 15:45 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 16:02 | Tomahock has left IRC (Tomahock!~Tomahock@190.119.163.98, Quit: Client closed) | |
| 17:22 | Tomahock has joined IRC (Tomahock!~Tomahock@190.119.163.98) | |
| 17:26 | <Tomahock> Hello, how can I see the level of workload in network traffic, ram usage of the clients connected to my LTSP on ubuntu server 18, I did the test on a thin client HP T5565 that has 890 RAM and 1 G of disk hard and it takes almost 3 minutes to load the desktop and then to be able to use the browser I notice it too slow, in parallel I am testing it in
| |
| 17:26 | virtual clients on a vmware workstation connected in bridge mode to the LTSP server network and there if the response is acceptable
| |
| 17:26 | The LTSP server has 10 virtual CPUs, 24 GB of RAM,
| |
| 17:26 | The server and the client are connected to the same switch.
| |
| 17:39 | <alkisg> To browse the web the clients need 4 GB RAM
| |
| 17:40 | If they only have 1GB either throw them away, or use a 32 bit operating system and don't use a browser
| |
| 17:41 | See also https://epoptes.org/documentation/lan-benchmark/
| |
| 17:58 | woernie has left IRC (woernie!~werner@www.velometrik.eu, Remote host closed the connection) | |
| 18:01 | <Tomahock> Hello, so with these hardware characteristics of the HP T5565 thin clients that I plan to use to use LTSP installed on ubuntu 18 as they are very slow from the clients, what version of ubuntu is lighter and adapts to those hardware capabilities of the tinclient indicated, I want the minimum users to navigate the internet and use open office
| |
| 18:01 | Here is the photo of the hardware characteristics of the HPT5565 thinclient
| |
| 18:01 | https://files.fm/u/tf6rt5cqz?k=d5ce6dcf#/view/tfb6eubxa
| |
| 18:02 | I have any chance with those Thinclient?
| |
| 18:14 | <vagrantc> any modern web browser is going to use more ram than you have available
| |
| 18:14 | a lot of sites will refuse to work with old browser ...
| |
| 18:15 | open office is also really heavy on resources
| |
| 18:27 | though most folks use libreoffice these days ... same issue though
| |
| 19:21 | wyre is back | |
| 19:23 | Tomahock has left IRC (Tomahock!~Tomahock@190.119.163.98, Ping timeout: 260 seconds) | |
| 20:04 | <alkisg> !cheap-client
| |
| 20:04 | <ltspbot> cheap-client: https://www.gearbest.com/tv-box-c_11262/?attr=2081-1279&odr=low2high
| |
| 20:06 | <alkisg> !forget cheap-client
| |
| 20:06 | <ltspbot> The operation succeeded.
| |
| 20:07 | <alkisg> Anyway, you can get i5 clients with 8 GB RAM with just 100€, don't bother with these ancient 20 years old clients that you have: https://www.ebay.com/itm/314457594048
| |
| 20:08 | Today's Internet needs at least 4 GB RAM, and older OS won't do it. You'd need an older Internet, which isn't available.
| |
| 20:09 | Even if you install a 10 years old browser, the memory usage will be high because the web pages use a lot more and heavier javascript / css / html nowadays, with higher resolution images etc, so they need more RAM than ever
| |
| 21:11 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 21:47 | <fiesh> I recently got myself a nanopi r5s, and have to say it's pretty amazing... I wonder how long it'll be until an ARM based ltsp client is the best choice
| |
| 21:47 | (it's also great as a router / server since it's got three rj45 connectors)
| |
| 21:53 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |
| 22:48 | wyre is now away: Auto away at Wed Apr 12 22:46:33 2023 UTC | |
| 22:52 | quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 3.8) | |
| 23:21 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50) | |
| 23:44 | quinox has joined IRC (quinox!~quinox@ghost.qtea.nl) | |