On 16-12-14 04:56:19, Ed Greshko wrote:
On 12/14/16 14:01, Ed Greshko wrote:
> I wonder if there is a race condition within the systemd processes
at times.....
I pretty much believe this to be the case since I've been doing some
extensive testing and
on a system that was consistently not showing the "sm-client.service:
Failed to read
PID..." message did show it once.
It happened immediately after erasing python2-systemd from my system
and about to report
that as my "solution" until I ran my test yet again and the message
didn't show up.
Also, the system I was testing on most often was a VM with 1-CPU
allocated. After I
assigned it 4-CPUs it no longer gets the "Failed to read PID" message.
My system also shows systemd complaining some of the time, either before
sendmail says anything, or after. In every case it says the service is
"active (running)". The system has 1 (old) cpu, and is running
Fedora20.
--
____________________________________________________________________
TonyN.:' <mailto:tonynelson@xxxxxxxxxxxxxxxxx>
' <http://www.georgeanelson.com/>
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
