| 29 Apr 2024 |
toonn | Thank you! Is the proper course of action always to ping here or should I learn the proper launchctl invocation? | 12:30:39 |
zowoq | Ping here or comment on https://github.com/nix-community/infra/issues/1245. | 12:34:28 |
| matthewcroughan changed their profile picture. | 13:00:17 |
toonn | Ok, thank you, zowoq <3 | 13:15:15 |
| NixOS Moderation Botchanged room power levels. | 15:29:21 |
| Frank Geusch joined the room. | 17:18:37 |
| Frank Geusch changed their display name from Frank Geusch to Master Fudge. | 17:28:04 |
matthewcroughan |
[matthewcroughan@aarch64:~]$ systemd-analyze
Startup finished in 33.091s (kernel) + 6min 56.468s (userspace) = 7min 29.560s
multi-user.target reached after 6min 56.456s in userspace.
| 18:40:15 |
matthewcroughan | * [matthewcroughan@aarch64:~]$ systemd-analyze
Startup finished in 33.091s (kernel) + 6min 56.468s (userspace) = 7min 29.560s
multi-user.target reached after 6min 56.456s in userspace.
| 18:40:22 |
matthewcroughan | Is that normal? 🤔 | 18:40:29 |
lassulus | Have you been slow in typing in your luks password? | 18:41:40 |
| roman.gonzalez left the room. | 20:49:28 |
| 30 Apr 2024 |
| @glaringweakness:nope.chat joined the room. | 10:48:02 |
| @firemercuty21:matrix.org changed their display name from ColemakSupremecist to ColemakSupremacist. | 13:58:23 |
tim | In reply to @matthewcroughan:defenestrate.it
[matthewcroughan@aarch64:~]$ systemd-analyze
Startup finished in 33.091s (kernel) + 6min 56.468s (userspace) = 7min 29.560s
multi-user.target reached after 6min 56.456s in userspace.
I think that also happens when you have units that take a long time and are required to finish for boot to be considered done, I had that recently with a restic backup that took some time to finish after boot, you can check right after boot with systemctl --running or something like that | 20:05:12 |
| ondt joined the room. | 22:23:40 |
| 1 May 2024 |
| azahi joined the room. | 14:23:05 |
| NixOS Moderation Botchanged room power levels. | 15:07:29 |
tim | In reply to @tim92:matrix.org I think that also happens when you have units that take a long time and are required to finish for boot to be considered done, I had that recently with a restic backup that took some time to finish after boot, you can check right after boot with systemctl --running or something like that systemctl list-jobs is the correct command | 15:17:06 |
| Grimmauld (moving to @grimmauld:grapevine.grimmauld.de) joined the room. | 19:34:07 |
raitobezarius | To nixos-hardware maintainers who may be interested: https://discourse.nixos.org/t/exciting-partnership-announcement-framework-community-nixos-communities-join-forces/44640 | 23:57:09 |
| 2 May 2024 |
| zodman joined the room. | 03:27:22 |
| Hayden joined the room. | 20:42:25 |
| 4 May 2024 |
| felschr joined the room. | 13:34:10 |
| 6 May 2024 |
| @dayvidpham:envs.net joined the room. | 05:40:52 |
| axel 🦀 left the room. | 08:21:16 |
| 7 May 2024 |
| nat changed their display name from nat to nat ⋆ ˚。⋆୨୧˚. | 21:21:44 |
| nat changed their profile picture. | 21:21:46 |
| pistache changed their display name from pistache to p̴͖͌i̵̼̔s̴̙̾t̶͕̀a̴͍̓c̸̞̉h̴̳͝e̴̠͗. | 23:23:32 |
| pistache changed their display name from p̴͖͌i̵̼̔s̴̙̾t̶͕̀a̴͍̓c̸̞̉h̴̳͝e̴̠͗ to pistache. | 23:24:40 |