Debian Bug report logs - #853769
opendkim: Default systemd service does not read the configuration file

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Georges Gouriten <georges@gouriten.name>

To: submit@bugs.debian.org

Subject: opendkim: Default systemd service does not read the configuration file

Date: Tue, 31 Jan 2017 18:48:26 +0100

Source: opendkim
Version: 2.11.0~alpha-8
Severity: important

Dear Maintainer,

I installed opendkim on a new server and had a problem, /etc/opendkim.conf was not read with "service opendkim start".

I fixed it by changing a line in /lib/systemd/system/opendkim.service

-ExecStart=/usr/sbin/opendkim -P /var/run/opendkim/opendkim.pid -p local:/var/run/opendkim/opendkim.sock
+ExecStart=/usr/sbin/opendkim -x /etc/opendkim.conf

The default does not seem convenient to me.

Best regards

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Message #12 received at 853769@bugs.debian.org (full text, mbox, reply):

From: Henrique de Moraes Holschuh <hmh@debian.org>

To: 853769@bugs.debian.org

Cc: 853769-submitter@bugs.debian.org

Subject: [PATCH] PROPOSED NMU

Date: Sat, 11 Feb 2017 14:50:34 -0200

[Message part 1 (text/plain, inline)]

Attached you will find a proposed NMU patch that should fix the issue,
as suggested by Georges Gouriten.

Note that I kept the -P and -p local: options, since that's how it
behaves in sysvinit.

Should I upload it?  This bug is threatening to kick out of the next
Debian stable all reverse dependencies of opendkim, including
cyrus-imapd.

-- 
  Henrique Holschuh

[proposed-NMU-opendkim-853769.patch (text/x-diff, attachment)]

Message #22 received at 853769@bugs.debian.org (full text, mbox, reply):

From: Scott Kitterman <scott@kitterman.com>

To: Henrique de Moraes Holschuh <hmh@debian.org>,853769@bugs.debian.org

Cc: 853769-submitter@bugs.debian.org

Subject: Re: Bug#853769: [PATCH] PROPOSED NMU

Date: Sat, 11 Feb 2017 17:43:33 +0000

Please don't upload.  I'll take care of it this week.

Scott K

On February 11, 2017 11:50:34 AM EST, Henrique de Moraes Holschuh <hmh@debian.org> wrote:
>Attached you will find a proposed NMU patch that should fix the issue,
>as suggested by Georges Gouriten.
>
>Note that I kept the -P and -p local: options, since that's how it
>behaves in sysvinit.
>
>Should I upload it?  This bug is threatening to kick out of the next
>Debian stable all reverse dependencies of opendkim, including
>cyrus-imapd.

Message #30 received at 853769@bugs.debian.org (full text, mbox, reply):

From: Henrique de Moraes Holschuh <hmh@debian.org>

To: Scott Kitterman <scott@kitterman.com>

Cc: 853769@bugs.debian.org, 853769-submitter@bugs.debian.org

Subject: Re: Bug#853769: [PATCH] PROPOSED NMU

Date: Sat, 11 Feb 2017 23:31:55 -0200

On Sat, 11 Feb 2017, Scott Kitterman wrote:
> Please don't upload.  I'll take care of it this week.

Ok.  Thanks.

-- 
  Henrique Holschuh

Message #38 received at 853769-done@bugs.debian.org (full text, mbox, reply):

From: Scott Kitterman <debian@kitterman.com>

To: 853769-done@bugs.debian.org

Subject: Re: opendkim: Default systemd service does not read the configuration file

Date: Mon, 20 Feb 2017 00:03:26 -0500

[Message part 1 (text/plain, inline)]

On Tue, 31 Jan 2017 18:48:26 +0100 Georges Gouriten <georges@gouriten.name> 
wrote:
> Source: opendkim
> Version: 2.11.0~alpha-8
> Severity: important
> 
> Dear Maintainer,
> 
> I installed opendkim on a new server and had a problem, /etc/opendkim.conf 
was not read with "service opendkim start".
> 
> I fixed it by changing a line in /lib/systemd/system/opendkim.service
> 
> -ExecStart=/usr/sbin/opendkim -P /var/run/opendkim/opendkim.pid -p 
local:/var/run/opendkim/opendkim.sock
> +ExecStart=/usr/sbin/opendkim -x /etc/opendkim.conf
> 
> The default does not seem convenient to me.

I've finally had time to investigate and test this claim and it is not 
correct.  As stated in the opendkim man page, the default config file is 
/etc/opendkim.conf, so there is no need to specify it.  

Using the existing service file I confirmed that changes in /etc/opendkim.conf 
do affect the configuration of the running service after it is restarted.  
There's no change needed.

Scott K

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.