You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently running Defender on SFOS Community edition on a PinePhone Pro and this dependency loop happens:
basic.targets depends on ...
paths.target which depends on ...
harbour-defender.path which depends on ..
home and unlocking home and all these things
which in turn depend on basic targets.
The recent systemd version in that SFOS version is actually able to detect the circular dependency, and solves it...
...by removing paths.target.
My suggestion would be to add DefaultDependencies=no in harbour's paths' units.
This way harbour's paths are started as part of paths.target, but there is no implicit "After=" in the target, thus it breaks the circular dependency, while the path is still scheduled for restart.
I'll make a PR.
The text was updated successfully, but these errors were encountered:
DrYak
added a commit
to DrYak/harbour-defender
that referenced
this issue
Oct 27, 2023
- fixes issue peterleinchen#8 : cyclic dependency in base.target that causes paths.target to be removed
- `DefaultDependencies=no` remove the implicit `After=` in paths.target
- the community encryption unlocker is a different service (decrypt-home_encrypted.service)
Currently running Defender on SFOS Community edition on a PinePhone Pro and this dependency loop happens:
The recent systemd version in that SFOS version is actually able to detect the circular dependency, and solves it...
...by removing paths.target.
My suggestion would be to add
DefaultDependencies=no
in harbour's paths' units.This way harbour's paths are started as part of paths.target, but there is no implicit "After=" in the target, thus it breaks the circular dependency, while the path is still scheduled for restart.
I'll make a PR.
The text was updated successfully, but these errors were encountered: