The main documentation for configuring sendmail is in a file at sendmail/cf/README. For some reason it isn't here on my 18.04 server.
Note that this file is referred to in other documentation within the sendmail/cf directories.
This is the complaint I get from systemd:
"opendkim.service: Can't open PID file /var/run/opendkim/opendkim.pid"
As seen here:
systemctl status opendkim.service
puts out this:
● opendkim.service - OpenDKIM DomainKeys Identified Mail (DKIM) Milter
Loaded: loaded (/lib/systemd/system/opendkim.service; enabled; vendor preset: enabled)
Active: deactivating (stop-sigterm) (Result: timeout)
Docs: man:opendkim(8)
man:opendkim.conf(5)
man:opendkim-genkey(8)
man:opendkim-genzone(8)
man:opendkim-testadsp(8)
man:opendkim-testkey
http://www.opendkim.org/docs.html
Process: 8217 ExecStart=/usr/sbin/opendkim -x /etc/opendkim.conf (code=exited, status=0/SUCCESS)
Tasks: 6 (limit: 2361)
CGroup: /system.slice/opendkim.service
└─8226 /usr/sbin/opendkim -x /etc/opendkim.conf
Feb 11 04:56:48 hacksaw.org systemd[1]: Starting OpenDKIM DomainKeys Identified Mail (DKIM) Milter...
Feb 11 04:56:48 hacksaw.org systemd[1]: opendkim.service: Can't open PID file /var/run/opendkim/opendkim.pid (yet?) after start: No such file or directory
Feb 11 04:56:48 hacksaw.org opendkim[8226]: OpenDKIM Filter v2.11.0 starting (args: -x /etc/opendkim.conf)
Feb 11 04:58:18 hacksaw.org systemd[1]: opendkim.service: Start operation timed out. Terminating.
If I start the daemon by hand, it goes. This seems to be about systemd.
Other data:
#ls -ld /var/run/opendkim/
drwxr-xr-x 2 opendkim opendkim 40 Feb 11 04:25 /var/run/opendkim/
The only line on the opendkim.conf:
UserID opendkim:opendkim
The default opendkim service file, from /lib/systemd/service:
[Unit]
Description=OpenDKIM DomainKeys Identified Mail (DKIM) Milter
Documentation=man:opendkim(8) man:opendkim.conf(5) man:opendkim-genkey(8) man:opendkim-genzone(8) man:opendkim-testadsp(8) man:opendkim-testkey http://www.opendkim.org/docs.html
After=network.target nss-lookup.target
[Service]
Type=forking
PIDFile=/var/run/opendkim/opendkim.pid
UMask=0007
ExecStart=/usr/sbin/opendkim -x /etc/opendkim.conf
Restart=on-failure
ExecReload=/bin/kill -USR1 $MAINPID
[Install]
WantedBy=multi-user.target
I want to configure an address on eth0:ipv4ll, even if eth0 is itself configured. Eth0 will never be configured with an ipv4ll address, it's set to DHCP. The system in question is used both in a regular network, and out of it, and needs to ipv4ll address all the time.
I set up a line in the interfaces file as such:
iface eth0:ipv4ll inet ipv4ll
But, this merely gets a log note that avahi-auotipd isn't configuring the interface because it already has a routable address on it.
Yes, eth0 has an address. But eth0:ipv4ll isn't eth0.
I can't figure out where exactly avahi-autoipd is being run, or I'd simply add --force-binding to the line.
Is there a better way?