00:53 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
01:19 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
03:50 | RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro) | |
04:02 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 240 seconds) | |
06:21 | RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.) | |
06:22 | RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro) | |
06:35 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
06:39 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
07:06 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
07:15 | woernie has joined IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de) | |
07:21 | woernie has left IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de, Ping timeout: 240 seconds) | |
07:23 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
07:37 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 260 seconds) | |
07:38 | woernie has joined IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de) | |
07:59 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
09:09 | woernie has left IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de, Ping timeout: 240 seconds) | |
09:10 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
09:12 | RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.) | |
09:13 | RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro) | |
09:13 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Ping timeout: 240 seconds) | |
09:14 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
09:17 | woernie_ has joined IRC (woernie_!~werner@pd9e8b5cc.dip0.t-ipconnect.de) | |
09:17 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 276 seconds) | |
09:54 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
10:39 | RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.) | |
10:53 | RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro) | |
13:44 | mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy) | |
14:15 | Guest55863 has left IRC (Guest55863!~lucascast@177.185.133.170, Quit: Leaving) | |
14:15 | lucascastro has joined IRC (lucascastro!~lucascast@177-185-133-170.dynamic.isotelco.net.br) | |
14:30 | jgee981350 has left IRC (jgee981350!~jgee@190.159.118.121, Quit: Ping timeout (120 seconds)) | |
14:30 | jgee981350 has joined IRC (jgee981350!~jgee@190.159.118.121) | |
15:50 | woernie_ has left IRC (woernie_!~werner@pd9e8b5cc.dip0.t-ipconnect.de, Ping timeout: 245 seconds) | |
15:51 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
17:03 | lucascastro has left IRC (lucascastro!~lucascast@177-185-133-170.dynamic.isotelco.net.br, Ping timeout: 260 seconds) | |
17:03 | alkis[m] has joined IRC (alkis[m]!alkismatri@gateway/shell/matrix.org/x-gwzvtjchdvawfees) | |
17:04 | <alkis[m]> Hi from matrix
| |
17:04 | <alkisg> alkis[m]: talking to yourself? :P
| |
17:24 | lucascastro has joined IRC (lucascastro!~lucascast@45-167-143-6.netfacil.inf.br) | |
17:31 | lucascastro has left IRC (lucascastro!~lucascast@45-167-143-6.netfacil.inf.br, Ping timeout: 240 seconds) | |
17:40 | lucascastro has joined IRC (lucascastro!~lucascast@177.185.131.162) | |
17:49 | lucascastro has left IRC (lucascastro!~lucascast@177.185.131.162, Ping timeout: 260 seconds) | |
17:49 | lucascastro has joined IRC (lucascastro!~lucascast@177-185-131-162.corp.isotelco.net.br) | |
18:17 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 260 seconds) | |
18:17 | woernie has joined IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de) | |
19:31 | woernie has left IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de, Remote host closed the connection) | |
19:43 | bobby90 has joined IRC (bobby90!6dc048e9@HSI-KBW-109-192-072-233.hsi6.kabel-badenwuerttemberg.de) | |
19:44 | <bobby90> @alksig - are you here?
| |
19:44 | <alkisg> bobby90: yup
| |
19:44 | <bobby90> unbelieveable... what TZ are you in? ;)
| |
19:44 | <alkisg> Greece, UTC+2 now
| |
19:45 | <bobby90> so, kali spera
| |
19:46 | <alkisg> To you too :)
| |
19:46 | <bobby90> just a small updae for you... I'm the guy where the KDE desktopsetings got corrupted through the LTSP.
| |
19:47 | <alkisg> Ah right, so what happenned?
| |
19:48 | <bobby90> I used Eclipse on the LTSP client, and on the next day, my .project file was gone. I also noticed some strange behaviour on the client. Maven builds were slow as hell and sometimes broke with some strange error message. This made me do some research.
| |
19:49 | I found on some (still rare) sources that some people consider sshfs less reliable than nfs, at least when load is high.
| |
19:50 | So my next step is to give nfs for /home a try. I will observe things for some time and eventually come back here and tellyou the story.
| |
19:51 | <alkisg> bobby90: I'm aware of certain file system functions that are not available on sshfs
| |
19:51 | That's why we're using nfs here; more stable and faster
| |
19:51 | But I haven't heard anything about data corruption
| |
19:51 | And if one wants security, I'd advice nfs over wireshark, which protects everything
| |
19:52 | (or nfsv4 + kerberos, which has integrated security)
| |
19:52 | <bobby90> Is that security thing a matter of encryption or authentication? which one is sacrificed on nfs?
| |
19:53 | <alkisg> Both
| |
19:53 | A person with a laptop in your LAN could see everything, if he knows how
| |
19:53 | <bobby90> So, someone who gains access to my network could access all user directories?
| |
19:53 | <alkisg> (i.e. local root account)
| |
19:53 | Yes
| |
19:53 | That's why sshfs is the default
| |
19:53 | <bobby90> I see.
| |
19:53 | <alkisg> (as wireshark is a new comer now, it wasn't available in the past)
| |
19:54 | <bobby90> Wireshark is a network analyzing tool to me... Is there something else with the same name?
| |
19:55 | <alkisg> wireguard, sorry, I'm frequently confusing the name
| |
19:55 | <bobby90> Ok, thanks
| |
19:55 | <alkisg> It's an in-kernel vpn
| |
19:55 | <bobby90> Interesting...
| |
19:55 | <alkisg> (old age... :D)
| |
19:55 | <bobby90> ;)
| |
19:55 | <alkisg> If you want to verify the sshfs issue, you could also try sshfs home in a standalone installation, without involving ltsp; if it happens there too, you'll know that sshfs is to blame
| |
19:56 | sshfs also has a few options with workarounds for known issues, but you'd need to investigate which one is that harms maven; if that's actually the case
| |
19:56 | lucascastro has left IRC (lucascastro!~lucascast@177-185-131-162.corp.isotelco.net.br, Ping timeout: 245 seconds) | |
19:56 | <bobby90> Difficult. I cannot reproduce the problem.
| |
19:57 | I have sshfs on a Raspberry Pi that runs my Jenkins instance. It does Maven builds with no problem so far.
| |
19:58 | However, much slower, of course. Some 30 seconds for one of my projects on my deelopment machine, 5 minutes on the Pi.
| |
19:59 | The sshfs mounts a share from a Synology Diskstation.
| |
20:01 | So I'm still wondering if this is an sshfs problem or maybe an sshfs-on-ubuntu-20.04 problem.
| |
20:02 | I'll keep investigating...
| |
20:08 | <alkisg> I've rarely seen such issues to be distro-specific
| |
20:09 | <bobby90> Ok
| |
20:12 | I have just hat a look at my sshfs configuration on the Pi. There is nothing special. On the other hand, the sshfs is just used to expose a git repository. So it's a rad-mostly connection. Eclipse access to a project will run at some higher scale.
| |
20:19 | Where would I put options to be used by sshfs?
| |
20:26 | <alkisg> bobby90: thousands of users are using sshfs without that issue; so IF that's the problem, it's related to the specific load
| |
20:26 | You can put it in SSH_OPTIONS in ltsp.conf
| |
20:27 | <bobby90> the server or clients section?
| |
20:27 | <alkisg> The clients section
| |
20:30 | <bobby90> Do I need to restart something after a change?
| |
20:30 | Or just log off and on again?
| |
20:42 | bobby90 has left IRC (bobby90!6dc048e9@HSI-KBW-109-192-072-233.hsi6.kabel-badenwuerttemberg.de, Quit: Connection closed) | |
20:43 | <alkisg> ltsp initrd, then client reboot
| |
20:50 | woernie has joined IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de) | |
21:22 | woernie has left IRC (woernie!~werner@pd9e8b5cc.dip0.t-ipconnect.de, Remote host closed the connection) | |
21:36 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
22:57 | RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.) | |