From d1fab3fe88ae873b26b50359758776ad9e31968e Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Thu, 7 Aug 2014 20:46:49 -0400 Subject: core: warn when merged units have conflicting dependencies A unit should not Conflict with itself. It also does not make much sense for a unit to be After or Before itself, or to trigger itself in some way. If one of those dependency types is encountered, warn, instead of dropping it silently like other dependency types. % build/systemd-analyze verify test/loopy3.service ... Dependency Conflicts dropped when merging unit loopy4.service into loopy3.service Dependency ConflictedBy dropped when merging unit loopy4.service into loopy3.service --- test/loopy4.service | 1 + 1 file changed, 1 insertion(+) create mode 120000 test/loopy4.service (limited to 'test/loopy4.service') diff --git a/test/loopy4.service b/test/loopy4.service new file mode 120000 index 0000000000..43e5658bcd --- /dev/null +++ b/test/loopy4.service @@ -0,0 +1 @@ +loopy3.service \ No newline at end of file -- cgit v1.2.3-54-g00ecf