search for: commstat

...s every five seconds. I cannot seem to find a way to reduce that chatter. I found the "Driver not connected" condition can refer to either the TCP connection down between 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...

...invalidated that assumption, IMHO, but that's a different rant.) > I found the "Driver not connected" condition can refer to either the TCP connection down between 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 m...