pldmd: improve reaction to mctpd socket close
pldmd: improve reaction to mctpd socket close

Previous behavior was to just log a "socket has been closed" message,
while the pldmd is still running an event loop. We're seeing the journal
contain a large number of these sometimes on Tacoma platforms. This is
likely a bug (either in pldmd or mctpd), yet to be determined.

Instead of flooding the journal, a better mechanism is to have the pldmd
exit the event loop and return with a failure reason code. This will
cause systemd to restart pldmd, which provides a chance for recovery.

Signed-off-by: Deepak Kodihalli <54105a30055f1e07853b8ee7a2f0d75d22ed98c1@in.ibm.com>
Change-Id: Iada6ee50808758312690883109f0499a8396e99e

openbmc/pldm,openbmc/pldm,openbmc/pldm