David Benfell writes:
Hi all,
This is still going awry
[root@munich]/home/benfell# systemctl status postfix
postfix.service - Postfix Mail Transport Agent
Loaded: loaded (/etc/systemd/system/postfix.service; enabled)
Active: failed (Result: exit-code) since Wed 2014-07-02 05:00:31 PD
I've had similar issues. Google for NetworkManager-wait-online.service and
you will probably find something to help. This is a service that uses
"nm-online" to wait for NetworkManager to report itself ready before
exiting. I can't remember all the details of making use of this, but one of
my system
Tim writes:
Sounds like a good idea to have something by default (i.e. as part the
system, not just a user kludge) that looks out for failed services post
boot, and tries to get them working after a small delay.
I'm about half-way to figuring out how to kludge this with:
systemctl --failed |
Hi all,
This is still going awry
[root@munich]/home/benfell# systemctl status postfix
postfix.service - Postfix Mail Transport Agent
Loaded: loaded (/etc/systemd/system/postfix.service; enabled)
Active: failed (Result: exit-code) since Wed 2014-07-02 05:00:31 PDT; 9h
ago
Process: 1
Allegedly, on or about 01 July 2014, David Benfell sent:
> For now, I'm modifying the afflicted service files and adding a cron
> job to run systemctl --failed.
Sounds like a good idea to have something by default (i.e. as part the
system, not just a user kludge) that looks out for failed service
Tom Horsley writes:
I gave up trying to analyze stuff like this soon after
systemd appeared,
It definitely does seem like systemd is a specialization all on its own.
Having used Arch Linux, I've been fighting it on and off for a while.
For now, I'm modifying the afflicted service files and
Rick Stevens writes:
On 07/01/2014 01:13 PM, David Benfell issued this missive:
Hi all,
I have no idea why this might be happening. I've looked at the systemd
control file for postfix and compared it to dovecot's. Both want the
network.target before starting.
"want" is a weakened version of
I gave up trying to analyze stuff like this soon after
systemd appeared, I just have a bunch of things in
my /etc/rc.d/rc.local file to restart various
services after a brief delay. Things like:
/bin/bash -c 'sleep 5 ; service stunnel restart' > /dev/null 2>&1 < /dev/null &
/bin/bash -c 'sleep 7 ;
David Benfell writes:
The difference is that dovecot starts correctly. Postfix does not. The
problem has only appeared since Saturday, when I probably did a yum
update.
I have since discovered that nsd also failed to start and that ejabberd
apparently failed to start correctly--pidgin on my
On 07/01/2014 01:13 PM, David Benfell issued this missive:
Hi all,
I have no idea why this might be happening. I've looked at the systemd
control file for postfix and compared it to dovecot's. Both want the
network.target before starting.
"want" is a weakened version of "requires". It doesn't
Hi all,
I have no idea why this might be happening. I've looked at the systemd
control file for postfix and compared it to dovecot's. Both want the
network.target before starting.
The difference is that dovecot starts correctly. Postfix does not. The
problem has only appeared since Saturday, when
11 matches
Mail list logo
