Syncthing init systemd in critical path?

[eikooc (jamie)]

Hi there. I am wondering why my computer waits for Syncthing-init.service to start? I.e. it is in the critical path of the boot. Is this understood correctly and is there a good reason? And is it possible to make the service not be part of the critical path?

❯ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @10.648s
└─multi-user.target @10.648s
  └─syncthing-init.service @3.963s +6.684s
    └─syncthing.service @3.961s
      └─network.target @3.926s
        └─wpa_supplicant.service @3.904s +18ms
          └─dbus.service @2.945s +61ms
            └─basic.target @2.927s
              └─sockets.target @2.926s
                └─podman.socket @2.920s +4ms
                  └─sysinit.target @2.880s
                    └─systemd-sysctl.service @2.853s +23ms
                      └─systemd-modules-load.service @449ms +2.383s
                        └─systemd-journald.socket @433ms
                          └─-.mount @417ms
                            └─-.slice @417ms

[calmh (Jakob Borg)]

@eikooc

Syncthing-init.service

This seems to be some sort of customisation, I’ve never seen it before. I think you need to figure out where it comes from to figure out what it’s intended to do. Google indicates it could be a NixOS-specific thing, if that’s what you’re running.

[eikooc (jamie)]

Hey @calmh. Thanks for the quick response. Yes I am running NixOS, so it might be specific to that, I’ll check how it is packaged in NixOS and reply back with my findings.