/lib/systemd/system/nfs-ganesha-lock.service uses .include which is deprecated #547
Comments
|
Any hints about what the drop-in file should look like? systemd docs aren't very helpful. |
|
https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/486938 I will update the debian packaging files accordingly once this change has been merged into 2.8 and 3 |
ffilz
pushed a commit
that referenced
this issue
Mar 20, 2020
#547 It seems the .include was for the "Conflicts=..." line. Some sites on the web say that for a Conflicts line you need to override the entire contents of the file. Systemd documentation is generally poor IMO, and there's little to no documentation about drop-in files in general and nothing about how to handle Conflicts= so this is my best guess at a drop-in file. Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com> Change-Id: I1b701406836d4bd4268b981913b34c7f04311fa2
dang
pushed a commit
to dang/nfs-ganesha
that referenced
this issue
Apr 20, 2020
nfs-ganesha#547 It seems the .include was for the "Conflicts=..." line. Some sites on the web say that for a Conflicts line you need to override the entire contents of the file. Systemd documentation is generally poor IMO, and there's little to no documentation about drop-in files in general and nothing about how to handle Conflicts= so this is my best guess at a drop-in file. Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com> Change-Id: I1b701406836d4bd4268b981913b34c7f04311fa2 (cherry picked from commit 8f58f8f)
dang
pushed a commit
to dang/nfs-ganesha
that referenced
this issue
Apr 27, 2020
nfs-ganesha#547 It seems the .include was for the "Conflicts=..." line. Some sites on the web say that for a Conflicts line you need to override the entire contents of the file. Systemd documentation is generally poor IMO, and there's little to no documentation about drop-in files in general and nothing about how to handle Conflicts= so this is my best guess at a drop-in file. Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com> Change-Id: I1b701406836d4bd4268b981913b34c7f04311fa2 (cherry picked from commit 8f58f8f)
dang
pushed a commit
that referenced
this issue
May 6, 2020
#547 It seems the .include was for the "Conflicts=..." line. Some sites on the web say that for a Conflicts line you need to override the entire contents of the file. Systemd documentation is generally poor IMO, and there's little to no documentation about drop-in files in general and nothing about how to handle Conflicts= so this is my best guess at a drop-in file. Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com> Change-Id: I1b701406836d4bd4268b981913b34c7f04311fa2 (cherry picked from commit 8f58f8f)
dang
pushed a commit
to dang/nfs-ganesha
that referenced
this issue
Jun 2, 2020
nfs-ganesha#547 It seems the .include was for the "Conflicts=..." line. Some sites on the web say that for a Conflicts line you need to override the entire contents of the file. Systemd documentation is generally poor IMO, and there's little to no documentation about drop-in files in general and nothing about how to handle Conflicts= so this is my best guess at a drop-in file. Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com> Change-Id: I1b701406836d4bd4268b981913b34c7f04311fa2 (cherry picked from commit 8f58f8f)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
systemd produces the following log message after installing nfs-ganesha:
/lib/systemd/system/nfs-ganesha-lock.service:2: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead.
Corresponding Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952406
The text was updated successfully, but these errors were encountered: