On 7/21/2018 11:21 AM, mick crane wrote:
On 2018-07-21 09:56, mick crane wrote:
On 2018-07-21 09:39, john doe wrote:
my interfaces file is identical and apache starts OK so it is
probably something else.
in /lib/systemd/system/apache2.target
do you have the "after" bit
1 [Unit]
2 Description=The Apache HTTP Server
3 After=network.target remote-fs.target nss-lookup.target
Or looking if "NetworkManager-wait-online.service" is enabled.
For systemd-networkd that is : "systemd-networkd-wait-online.service".
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
If your '/etc/network/interfaces' file is empty with the exception of
the 'lo' interface, your interfaces are probably handled by an other
"program" and you need to determine which "program" is responsible for
your interfaces.
I'm quite cheerful as everything seems to be working but it wouldn't
hurt to find out and may assist OP.
Appologies for the confusion, I read your answer and think I could add
to it but was not in anycase directed towards you! :)
Yes, my comment was for the OP (taking into account other answers he has
sent to the list).
Can you give clue where to look ?
Not knowing much about systemd
The service 'systemd-networkd' looks among other directories in
'/etc/systemd/network'.
https://www.freedesktop.org/software/systemd/man/systemd-networkd.service.html
One hint to determine how your interfaces are configured could be to
look at the top of the file '/etc/resolv.conf'. If you have some comment
lines there, those comments might indicate which "PRG" is handeling your
INTs.
Also, has said above, if your '/etc/network/interfaces' only contains
the 'lo' interface you can probably eliminate dhclient for configuring
your DHCP interface.
just quickly looking
/etc/default/networking
seems that the default is to wait for all interfaces ?
As far as I understand it, '/etc/default/networking' is only useful at
boot or when executing '/etc/init.d/networking' (systemd way: $
systemctl ... networking.service).
--
John Doe
