IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 5 September 2023 (all times are UTC)
| 04:29 | woernie has joined IRC (woernie!~werner@p5ddedeef.dip0.t-ipconnect.de) | |
| 04:30 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: buh bye) | |
| 04:31 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 04:35 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Client Quit) | |
| 04:35 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 05:23 | wyre is back | |
| 06:02 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 06:17 | wyre is now away: Auto away at Tue Sep 5 06:12:29 2023 UTC | |
| 06:57 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 06:58 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 07:19 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection) | |
| 07:20 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 08:05 | XYZ_ has left IRC (XYZ_!~XYZ@78-80-106-89.customers.tmcz.cz, Remote host closed the connection) | |
| 08:12 | XYZ_ has joined IRC (XYZ_!~XYZ@78-80-106-89.customers.tmcz.cz) | |
| 10:49 | alkisg has left IRC (alkisg!~Thunderbi@srv1-dide.ioa.sch.gr, Ping timeout: 260 seconds) | |
| 10:49 | alkisg has joined IRC (alkisg!~Thunderbi@2a02:587:7444:7900:56e0:4cff:fe68:d) | |
| 13:43 | highvoltage has left IRC (highvoltage!~highvolta@shell.jonathancarter.org, Server closed connection) | |
| 13:43 | highvoltage has joined IRC (highvoltage!~highvolta@shell.jonathancarter.org) | |
| 13:43 | highvoltage is now away: traveling, consider email instead | |
| 14:27 | <Hyperbyte> Hi alkisg. :-)
| |
| 14:41 | I have LTSP running on a site with some network problems... however, because of reasons too boring to go into, I cannot debug those problems currently. The issue I have is that whenever a network connection becomes unavailable for a few seconds or minutes, workstations crash. Is this normal with LTSP? Often workstations are unresponsive with squashfs errors on the console.
| |
| 14:42 | Ideally LTSP would keep the connection to the server alive until it becomes responsive again, but it seems to actually disconnect if the network or server is unavailable for a little bit.
| |
| 15:22 | <alkisg> Hyperbyte: NFS will reconnect even after days. SSHFS will keep the connection alive for 2 hours 11 minutes. But of course it won't ever reconnect (as in re-authenticate), it will only keep the connection alive (so e.g. it won't work on server reboot)
| |
| 15:25 | Vercas5 has joined IRC (Vercas5!~Vercas@gateway/tor-sasl/vercas) | |
| 15:26 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 246 seconds) | |
| 15:26 | Vercas5 is now known as Vercas | |
| 15:39 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 15:49 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 15:55 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 246 seconds) | |
| 15:59 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 16:17 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 246 seconds) | |
| 17:31 | ltspbot` has left IRC (ltspbot`!~supybot@devs.ts.sch.gr, Server closed connection) | |
| 17:32 | ltspbot has joined IRC (ltspbot!~supybot@devs.ts.sch.gr) | |
| 18:21 | <Hyperbyte> alkisg, that's weird. It seems to be much more sensitive than that. So technically, if I disconnect the network cable and reconnect, it should work fine still?
| |
| 18:29 | <alkisg> Yes
| |
| 18:30 | Assuming you're using the new ltsp and not the old one, as nbd is much more sensitive
| |
| 19:22 | woernie has left IRC (woernie!~werner@p5ddedeef.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 20:04 | wyre is back | |
| 21:10 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 22:36 | wyre is now away: Auto away at Tue Sep 5 22:32:03 2023 UTC | |