!DBFhtjpqmJNENpLDOv:nixos.org

NixOS systemd

611 Members
NixOS ❤️ systemd172 Servers

Load older messages

SenderMessageTime
21 Feb 2025
@elvishjerricco:matrix.orgElvishJerricco x-systemd.required-by= will make it so that the mount is not required by loca-fs.target, but instead just by the value of the option 06:01:41
@elvishjerricco:matrix.orgElvishJerriccomeaning if it fails, it won't send the system to emergency mode06:01:54
@elvishjerricco:matrix.orgElvishJerricco but of course a required-by relationship isn't an ordering relationship, hence why I also mentioned x-systemd.before= 06:02:38
@cleverca22:matrix.orgcleverca22 ElvishJerricco: ah, RequiresMountsFor is what i wanted, and does work 06:09:18
@cleverca22:matrix.orgcleverca22 but only if its in unitConfig, doh 06:09:23
@cleverca22:matrix.orgcleverca22 service.d/overrides.conf:18: Unknown key name 'RequiresMountsFor' in section 'Service', ignoring. 06:09:34
@elvishjerricco:matrix.orgElvishJerricco cleverca22: Sure, though that requires adding nofail to the file system if you want it to not cause emergency mode 06:10:05
@cleverca22:matrix.orgcleverca22yep, i already added nofail, and that caused an issue of the service starting without the disk06:12:43
@cleverca22:matrix.orgcleverca22 nofail plus RequiresMountsFor results in no emergency mode, and the service doesnt start 06:13:01
@cleverca22:matrix.orgcleverca22 Feb 21 06:10:16 backend1 systemd[1]: ipfs.service: Job ipfs.service/start failed with result 'dependency'. 06:13:32
@cleverca22:matrix.orgcleverca22thats perfect06:13:35
@elvishjerricco:matrix.orgElvishJerricco yea, that's nearly the same thing as simply adding x-systemd.required-by=foo.service,x-systemd.before=foo.service, with the only difference being that my way doesn't mount the file system if foo.service isn't scheduled at boot. 06:15:29
@cleverca22:matrix.orgcleverca22under normal conditions, it should mount at boot, and start the service at boot06:19:59
@elvishjerricco:matrix.orgElvishJerriccoyea, the difference is negligible06:20:12
@cleverca22:matrix.orgcleverca22 the problem, is that somebody put the fileSystems config in a shared module
and then deployed it to a dev machine in digital ocean
a machine lacking the DO volume.... 		06:20:26
@elvishjerricco:matrix.orgElvishJerriccoit would only matter if you wanted to mask the service for some reason06:20:27
@cleverca22:matrix.orgcleverca22so the machine instantly fell over06:20:32
@cleverca22:matrix.orgcleverca22and nobody bothered fixing it, for 5 months06:20:39
@elvishjerricco:matrix.orgElvishJerriccoIt'll mount at normally boot with either way06:21:28
@elvishjerricco:matrix.orgElvishJerricco but the x-systemd. way would not mount if you masked the service for some reason 06:21:54
@elvishjerricco:matrix.orgElvishJerricco* It'll mount normally at boot with either way06:22:02
@cleverca22:matrix.orgcleverca22ah06:22:13
24 Feb 2025
@ubalot:matrix.orgubalot joined the room.08:06:23
@arianvp:matrix.orgArian

Do I need to worry about these logs in systemd-initrd?


initrd-linux> Warning: Couldn't satisfy dependency libc.so.6 for "/nix/store/8d9rkvllf04pyz790vk6wd4k8mnc5c64-glibc-2.40-36/lib/libnss_files.so.2"
initrd-linux> Warning: Couldn't satisfy dependency ld-linux-aarch64.so.1 for "/nix/store/8d9rkvllf04pyz790vk6wd4k8mnc5c64-glibc-2.40-36/lib/libc.so.6"
initrd-linux> Warning: Couldn't satisfy dependency libc.so.6 for "/nix/store/8d9rkvllf04pyz790vk6wd4k8mnc5c64-glibc-2.40-36/lib/libm.so.6"
initrd-linux> Warning: Couldn't satisfy dependency ld-linux-aarch64.so.1 for "/nix/store/8d9rkvllf04pyz790vk6wd4k8mnc5c64-glibc-2.40-36/lib/libm.so.6"
initrd-linux> Warning: Couldn't satisfy dependency libc.so.6 for "/nix/store/8d9rkvllf04pyz790vk6wd4k8mnc5c64-glibc-2.40-36/lib/libdl.so.2"
initrd-linux> Warning: Couldn't satisfy dependency libc.so.6 for "/nix/store/8d9rkvllf04pyz790vk6wd4k8mnc5c64-glibc-2.40-36/lib/libpthread.so.0"
initrd-linux> Warning: Couldn't satisfy dependency libc.so.6 for "/nix/store/mjqj5naakm09gfvwm8aalbzswdqwm9v5-gcc-13.3.0-libgcc/lib/libgcc_s.so.1"
initrd-linux> Warning: Couldn't satisfy dependency libc.so.6 for "/nix/store/04aq2w58qlqjvwamcljh1hahz744hlzd-libidn2-2.3.7/lib/libidn2.so.0.4.0"
initrd-linux> Warning: Couldn't satisfy dependency ld-linux-aarch64.so.1 for "/nix/store/04aq2w58qlqjvwamcljh1hahz744hlzd-libidn2-2.3.7/lib/libidn2.so.0.4.0"
initrd-linux> Warning: Couldn't satisfy dependency libc.so.6 for "/nix/store/8d9rkvllf04pyz790vk6wd4k8mnc5c64-glibc-2.40-36/lib/libresolv.so.2"
initrd-linux> Warning: Couldn't satisfy dependency ld-linux-aarch64.so.1 for "/nix/store/8d9rkvllf04pyz790vk6wd4k8mnc5c64-glibc-2.40-36/lib/libresolv.so.2"
initrd-linux> Warning: Couldn't satisfy dependency libc.so.6 for "/nix/store/8rywcj8s7gx9iy4hwipfz7nb87s9rib9-libunistring-1.2/lib/libunistring.so.5.1.0"
initrd-linux> Warning: Couldn't satisfy dependency ld-linux-aarch64.so.1 for "/nix/store/8rywcj8s7gx9iy4hwipfz7nb87s9rib9-libunistring-1.2/lib/libunistring.so.5
10:02:26
@arianvp:matrix.orgArian we are including libnss_files so I am confused. Also ld-linux-aarch64.so.1 missing sounds bad? 10:02:47
@arianvp:matrix.orgArianoh wait our ld-linux is just a stab that says “this doesn’t work” anyway10:11:18
@arianvp:matrix.orgArianah this is just glibc being glibc10:32:55
@elvishjerricco:matrix.orgElvishJerriccoThis happens because glibc is effectively an implicit part of RPATH. So all the glibc libs are not found in the literal RPATH of an executable, but are found by the dynamic loader because it just knows to look there20:57:53
@arianvp:matrix.orgArian I just found out that systemd-fstab has a —generate-fstab flag that uses MountPoints= to synthesize an fstab file 22:07:34
@arianvp:matrix.orgArian * I just found out that systemd-repart has a —generate-fstab flag that uses MountPoints= to synthesize an fstab file 22:07:42

Show newer messages

Back to Room ListRoom Version: 6