search for: drvnotconn

...ween the client and the server (fd < 0), or between the server and the device driver or the device driver and the UPS (commstate <> 1). The attached patch to pullups() in clients/upsmon.c suppresses the messages sent to /var/log/messages every five seconds when commstate <> 1, since DRVNOTCONN is actually expected in that case. There is another place in try_connect() in clients/upsmon.c that causes messages to be written to /var/log/message every five seconds when a TCP connection cannot be made from the client to the server. (I test this failure scenario by killing the server upsd.)...

...ween the client and the server (fd < 0), or between the server and the device driver or the device driver and the UPS (commstate <> 1). The attached patch to pullups() in clients/upsmon.c suppresses the messages sent to /var/log/messages every five seconds when commstate <> 1, since DRVNOTCONN is actually expected in that case. > > There is another place in try_connect() in clients/upsmon.c that causes messages to be written to /var/log/message every five seconds when a TCP connection cannot be made from the client to the server. (I test this failure scenario by killing the serve...