| 26 May 2021 |
 alexey96 | * UPD: fixed the problem by trial and error. Adding environment.etc = { "resolv.conf".text = "nameserver 192.168.1.100\n"; }; to configuration.nix reduced cpu usage and there is no more looping. | 14:39:40 |
| 27 May 2021 |
 andi- | https://github.com/systemd/systemd/pull/19743 🎉 | 09:42:34 |
|  teto joined the room. | 10:35:48 |
 NinjaTrappeur | Nice! | 14:11:27 |
|  telent joined the room. | 14:52:36 |
|  Fabian Affolter joined the room. | 18:03:18 |
|  morrpl joined the room. | 20:35:13 |
| 28 May 2021 |
|  ijustwannalurk left the room. | 05:37:21 |
|  Patrick Georgi left the room. | 09:49:14 |
| 29 May 2021 |
|  justinrestivo changed their display name from justinrestivo to oh caml >>=. | 12:21:01 |
| justinrestivo changed their profile picture. | 12:22:01 |
| justinrestivo changed their display name from oh caml >>= to justinrestivo. | 12:22:30 |
| justinrestivo changed their profile picture. | 12:24:01 |
 hpfr | anyone know why umask 077; wg genkey > wg-private gives me Warning: writing to world accessible file. Consider setting the umask to 077 and trying again.? Not sure if NixOS or fish is involved, but this seems to work for everyone on the web | 19:07:09 |
 Roos | afair, umask(2) affect's the current process mask. So it should be a shell builtin. | 19:10:18 |
| hpfr | hmm, it doesn't seem to work in bash either, even though umask in both fish and bash confirms it's been set to 0077 after umask 077 | 19:16:54 |
| hpfr | ahh, I think it was because I had already created the file with different permissions and tried to overwrite without removing. works after removing | 19:18:00 |
| Roos | I think some shells (all?) truncate the file if it already exists prior to writing. | 19:18:59 |
| hpfr | yeah, but the truncated empty file will still exist with preexisting perms | 19:22:18 |
