Hello Roland, thanks for your report!
On Mon, 8 Jan 2018 10:50:49 +0100 Roland Rosenfeld <[email protected]> wrote: > I use arpwatch via systemd, but had to notice, that arpwatch tries to > start up before the network interface is fully up (some spanning tree > issue). This leads to arpwatch failing and not correctly starting up. > > [log snippet removed] > > I think that arpwatch should wait until the interface is up, so I > created the following > /etc/systemd/system/[email protected]/override.conf which fixes > the issue for me: > > [Unit] > After=network-online.target > > [Install] > Wants=network-online.target > > Maybe it would be a good idea to add something like this to > /lib/systemd/system/[email protected] You are right, the current state definitely needs fixing. Currently the per-instance unit file doesn't even wait for network.target (which was what I had originally intended, but PartOf does not actually do that). But since arpwatch reads the interface's configuration, network-online makes sense. I'll add the network-online.target dependency to the [email protected] file as you suggested. Note that the "Wants=" directive should also be part of the [Unit] section as per documentation. Thanks & regards Lukas
pgp3Vf_tVu0cn.pgp
Description: OpenPGP digital signature
