On 16 October 2015 at 21:17, Kevin Chadwick <[email protected]> wrote:
> > > > > > For testing purposes, I changed my smtpd.conf to listen on 127.0.0.1 > > > instead of enp0s4 and it did not crash on startup, so that tells me > that > > > our > > > troubleshooting is on the right track. > > > > > > > Hmm, I also did some testing. I added "ExecStartPre=/usr/bin/ip a" to the > > smtpd service. That showed that the interface smtpd should listen on is > > already configured by the time smtpd starts, but it still fails with > > "fatal: smtpd: bind: Cannot assign requested address". > > > > I also ran smtpd straced, but that made the main process exit with > status 1 > > without reporting any error. So that didn't really help. I'm really > curious > > what address smtpd is trying to bind to. > > > > -- > > Maarten > > Nothing personal and I hope you get it sorted soon but I can't help > LMAO when I consider the arch list telling me systemd was "simpler", oh > and NTP was simple and so why it hadn't had any security bugs found > among other things that have proven false/true! (At the same time I > completely accept that it takes little skill but care and time to > play it safe) > > I have always much preferred OpenBSD's rc scripts and init to most if > not all and don't like parallel start especially on HDD but how > about trying OpenRC or OpenBSD even? > > Would that not solve this problem perhaps with added benefits WRT > OpenBSD usage? > > Seriously, could we not turn this into a systemd discussion? So far it looks like systemd is not the culprit. If you got reason to suspect otherwise or ideas how to fix it, I'm all ears. But other than that I don't care which init system is better or evil. Thanks. -- Maarten
