On Wed, 23 May 2007 02:58:55 +0400, Peter Selinger <[EMAIL PROTECTED]> wrote:
>> Let's think about it now. We have a well-defined path to the error -- all >> I have to do is delete those two lines in my ups.conf. What can be done >> in the code to make it emit a message that isn't a blank stone wall? Or, >> to put it another way, what can we do so that the users list will never >> have to hear this question again? > > Well, the actual driver should print some message at debug level 0 > before croaking. Like "I didn't recognize this UPS; please try > specifying the vendorid and/or subdriver parameters". I don't think it > can be handled by upsdrvctl itself, as it can't know why some > particular driver fails. The bad news is that it has to be done in > each driver separately. > > Alexander, can you do that? > > Some other drivers, like newhidups, already do such a thing; see e.g. > drivers/belkin-hid.c:404-408. > No problem, did that. -- Alexander _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
