Re: postfix boot dependencies with systemd
On Sat, Jan 26, 2019 at 10:13:10PM +1100, Russell Coker wrote:
It appears that the boot of my laptop is delayed by postfix depending on network-online.target. How can I change this? Postfix is only listening on 127.0.0.1 so there's no reason for it to wait until my laptop connects to the Wifi network before continuing the boot.
I ran "systemctl edit postfix@-" and "systemctl edit postfix@" and put the below in which should make it not depend on network-online.target. But it doesn't change anything. Any ideas?
is there a loopback only target you can make it depend on rather than network-manager? other than that, my only idea is to dump network manager and manually configure your network with /etc/interfaces. I've always found that's best, anyway - NM is OK-ish for the simplest of network configs but a complete PITA for anything even slightly complex. craig -- craig sanders <cas@taz.net.au> BOFH excuse #44: bank holiday - system operating credits not recharged
On Saturday, 26 January 2019 11:34:26 PM AEDT Craig Sanders via luv-main wrote:
On Sat, Jan 26, 2019 at 10:13:10PM +1100, Russell Coker wrote:
It appears that the boot of my laptop is delayed by postfix depending on network-online.target. How can I change this? Postfix is only listening on 127.0.0.1 so there's no reason for it to wait until my laptop connects to the Wifi network before continuing the boot.
I ran "systemctl edit postfix@-" and "systemctl edit postfix@" and put the below in which should make it not depend on network-online.target. But it doesn't change anything. Any ideas?
is there a loopback only target you can make it depend on rather than network-manager?
There doesn't appear to be. Google searches indicate not.
other than that, my only idea is to dump network manager and manually configure your network with /etc/interfaces. I've always found that's best, anyway - NM is OK-ish for the simplest of network configs but a complete PITA for anything even slightly complex.
My laptop has a very simple network configuration, connect to whatever Wifi or Ethernet is available and route everything through it. It's also a very annoying configuration to run in any other way due to the dozen or so Wifi networks I connect to. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
Hello Russell and Craig, On 1/27/19, Russell Coker via luv-main <luv-main@luv.asn.au> wrote:
On Saturday, 26 January 2019 11:34:26 PM AEDT Craig Sanders via luv-main wrote:
On Sat, Jan 26, 2019 at 10:13:10PM +1100, Russell Coker wrote:
It appears that the boot of my laptop is delayed by postfix depending on network-online.target. How can I change this? Postfix is only listening on 127.0.0.1 so there's no reason for it to wait until my laptop connects to the Wifi network before continuing the boot.
is there a loopback only target you can make it depend on rather than network-manager?
There doesn't appear to be. Google searches indicate not.
other than that, my only idea is to dump network manager and manually configure your network with /etc/interfaces. I've always found that's best, anyway - NM is OK-ish for the simplest of network configs but a complete PITA for anything even slightly complex.
My laptop has a very simple network configuration, connect to whatever Wifi or Ethernet is available and route everything through it. It's also a very annoying configuration to run in any other way due to the dozen or so Wifi networks I connect to.
Very interesting. This relates to why I would prefer less monolithic "solutions" than Systemd and NetworkManager. It is also what I want to find, but appears to not be available, yet, some simpler framework or daemon that will handle Wi-Fi connections, even just one routine one. If I knew enough about the ways to manage the connection manually, I would not need the tool, but not being sufficiently conversant with the detail of connecting, nor beyond smaller simpler programming, I cannot make the tool. I have found the underlying assumptions in NetworkManager a real pain and frustrating. I have found that it will proceed to make the first connection the default route, regardless of whether that is suitable, and unduly difficult to change. That made life difficult while on dial up, and wanting to use an ethernet cable to another PC, and consider a network printer. I was bringing up the modem and the connection manually, running the computer in local mode most of the time. I really dislike Lennart Poettering and his attitudes. Regards, Mark Trickett
On Sunday, 27 January 2019 8:23:10 AM AEDT Mark Trickett via luv-main wrote:
is there a loopback only target you can make it depend on rather than network-manager?
There doesn't appear to be. Google searches indicate not.
other than that, my only idea is to dump network manager and manually configure your network with /etc/interfaces. I've always found that's best, anyway - NM is OK-ish for the simplest of network configs but a complete PITA for anything even slightly complex.
My laptop has a very simple network configuration, connect to whatever Wifi or Ethernet is available and route everything through it. It's also a very annoying configuration to run in any other way due to the dozen or so Wifi networks I connect to.
Very interesting. This relates to why I would prefer less monolithic "solutions" than Systemd and NetworkManager. It is also what I want to find, but appears to not be available, yet, some simpler framework or daemon that will handle Wi-Fi connections, even just one routine one.
Less monolithic solutions don't solve problems, they just give you different problems. The other problem is that some daemons can't start until networking is operational. Sometimes the solution to this without systemd is to put sleep statements in the start scripts, which then means that you get delays you don't need to have.
I have found the underlying assumptions in NetworkManager a real pain and frustrating. I have found that it will proceed to make the first connection the default route, regardless of whether that is suitable, and unduly difficult to change. That made life difficult while on dial up, and wanting to use an ethernet cable to another PC, and consider a network printer. I was bringing up the modem and the connection manually, running the computer in local mode most of the time.
Yes that's a difficult thing (from what I know about NetworkManager).
I really dislike Lennart Poettering and his attitudes.
https://www.youtube.com/watch?v=o_AIw9bGogo This is worth watching. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
participants (3)
-
Craig Sanders -
Mark Trickett -
Russell Coker