This was causing the /etc/resolv.conf file to be always updated when
  RESOLV_MODS was not set...

  Before the commit 5d6156454bf8f6dab4a5fdd7e1bf6 we were not updating
  the /etc/resolv.conf file if the RESOLV_MODS was empty.

  See https://bugzilla.redhat.com/show_bug.cgi?id=1610411 for more info.

  This partially reverts the commit 15eaf7ece, because systemd's
  generated unit files might have incorrect dependencies at some
  circumstances, thus causing diskless nfs-clients to hang while
  unmounting root filesystem after '$ service network stop'.

  Since we are using systemd, the Default-Start/Stop keywords were
  omitted. Basically the LSB header is quite similar to LSB header of
  network service...

  Previously, there were 2 additional conditions related to this part of
  code, but they were removed in time, so this last condition has
  remained an artifact and is de-facto obsolete.

  However, the 'pidof -x dhclient' condition could cause the network
  service to hang on stop/restart when processes were executed from a
  network share... Removing that condition should hypothetically fix it.

  For currently unknown reason the dbus-send calls will fail to set the
  firewall zone for the given interface if we omit the --print-reply
  option...

  This looks like some kind of race-condition in dbus-send, since the
  --print-reply makes the call synchronous and slower.

  Hopefully this is only a temporary workaround until DBus is fixed.

  Resolves: #1586284

  Resolves: RHBZ#1583677