2008/2/19, Arjen de Korte <[EMAIL PROTECTED]>: > >> First of all, it helps if you post the *full* line from the logs and > >> also show some context (how often these messages occur). > > That was the *full* line from the logs, except the syslog timestamp. > > But I hardly think the timestamp and the hostname could be at any use > > here. > > We need the timestamp in order to find out what goes wrong and how often > it goes wrong. This is *very* relevant information. > > [...] > > >> Before all, upgrade to nut-2.2.1. > > Now, I've done the upgrade, after a few adjustments to the ports > > Makefile I will submit the patches to the FreeBSD ports collection, so > > everyone can make use of 2.2.1. > > I don't know if you mentioned this before, but FreeBSD might be part of > the problem here. We have seen numerous problems with that in the past > because of the 'libusb' implementation is different from what is common in > Linux. Especially handling interrupt reports is handled different. I'm not > an expert in FreeBSD, so I don't know of the fine details.
the libusb 1.0 project I mentioned the other day might give us a chance to finally solve these issues... Arnaud -- Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ Free Software Developer - http://arnaud.quette.free.fr/ _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
