corrupted checksums happen all the time with the 6-port serial card,
even when only using one port (and I don't give a shit about the other
ports, if anybody has a one-port laying around...)
so stop whining already.
$OpenBSD$
--- drivers/bcmxcp_ser.c.orig Wed Aug 23 11:15:54 2006
+++ drivers/bcmxcp_ser.c Wed Aug 23 11:26:37 2006
@@ -168,8 +168,8 @@ int get_answer(unsigned char *data, unsi
/* now we have the whole answer from the ups, we can checksum it */
if (!checksum_test(my_buf)) {
- ser_comm_fail("checksum error! ");
- return -1;
+ upsdebugx(2, "checksum error!");
+ return -1;
}
memcpy(data+end_length, my_buf+4, length);
--
Henning Brauer, hb@bsws.de, henning@openbsd.org
BS Web Services, http://bsws.de
OpenBSD-based Webhosting, Mail Services, Managed Servers, ...
Dear Henning, did you know that your system log is configurable? See the man pages for sysklogd(8) and syslog.conf(5). "Info" is the lowest log level besides "debug", and is the appropriate log level for messages on users logging in and out. If you don't like to see these messages in your system log, configure your syslog to log only "notice" and higher. Communications failures due to faulty hardware (such as you seem to have) are appropriate to be logged at the "warning" level. If you don't like to see these messages in your system log, configure your syslog to log only "error" and higher. I find the tone of your message offensive, and I would ask you to keep your anger to yourself. I know you probably feel that all NUT developers have been conspiring just to make your day miserable, and that we all have faulty 6-port serial cards behaving exactly like yours. However, this is not the case. In general, you will find that people are more eager to spend their private time helping you if you ask politely. -- Peter Henning Brauer wrote:> > corrupted checksums happen all the time with the 6-port serial card, > even when only using one port (and I don't give a shit about the other > ports, if anybody has a one-port laying around...) > so stop whining already. > > $OpenBSD$ > --- drivers/bcmxcp_ser.c.orig Wed Aug 23 11:15:54 2006 > +++ drivers/bcmxcp_ser.c Wed Aug 23 11:26:37 2006 > @@ -168,8 +168,8 @@ int get_answer(unsigned char *data, unsi > > /* now we have the whole answer from the ups, we can checksum it */ > if (!checksum_test(my_buf)) { > - ser_comm_fail("checksum error! "); > - return -1; > + upsdebugx(2, "checksum error!"); > + return -1; > } > > memcpy(data+end_length, my_buf+4, length); > > > > > -- > Henning Brauer, hb@bsws.de, henning@openbsd.org > BS Web Services, http://bsws.de > OpenBSD-based Webhosting, Mail Services, Managed Servers, ... > > _______________________________________________ > Nut-upsdev mailing list > Nut-upsdev@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev >
[still on small deserved holidays, but forced to enter the round in that kind of thread!] first thing first, be constructive in your mails. Most nut developers and contributors are benevolants, as for other FLOSS developers. It's rare to have a "kudos" mail for our work, and your mail (as shown) are offensive to most of us! Next, about your issues: 1) the fact that you're seing "new connexion" msg is either due to real unsolicited connexions, but most probably to the fact that you're using a exotic monitoring method (== not upsmon). There is a session mechanism, as used in upsmon, that prevent that kind of logs. So you might be using some kind of upsc in a shell script, which might be considered bad as it cause your kind of issue. Otherwise, you'll have to use upsd's ACL to avoid unsollicited connexions... Finally, and as told by Peter, there are (or should be) configurable mechanisms in your logd daemon. If not, consider bugging obsd people to switch to something more appropriate. 2) the driver is not buggy. If you face wrong chksum, it's really that the board is buggy! I'm not sure about the firmware pb (too quickly read the thread) Finally, I understand the hanger of being borred by such things. And we are open to discussion (the proofs are that your mails have been approved, though you're not subscribed, and that I'm considering your patch). But you shouldn't think you've got almighty knowledge because you run obsd. Once more, there are ways to report problems, ask for info, and submit patches in the FLOSS world. And this is definitively not the path you've taken first. Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/
Henning Brauer wrote:> > * Peter Selinger <selinger@mathstat.dal.ca> [2006-08-23 16:21]: > > I find the tone of your message offensive, and I would ask you to keep > > your anger to yourself. I know you probably feel that all NUT > > developers have been conspiring just to make your day miserable, and > > that we all have faulty 6-port serial cards behaving exactly like > > yours. However, this is not the case. In general, you will find that > > people are more eager to spend their private time helping you if you > > ask politely. > > and I really need no stupid PC lessonsAnd I really don't need to help you with your NUT problems. Nor does anyone else. Sheesh! -- Peter P.S. please keep list traffic on the mailing list.