Is this an environment issue rather than a boot order issue? Does it come up if you launch it from cron or batch rather than directly at the command line?ED.
This would make sense based on the fact that the network is up. When I start smptd myself from the command line, I'm still using systemd to do it. #systemctl start smtpd.service I would think that the environment would be the same when systemd starts it up at boot... but at this point I'm willing to pursue any avenue. -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
