On Friday 25 February 2005 11:01, Samuele Giovanni Tonon wrote: > hi, > A bug request was filled against debian: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296648 > > i think that this is most a feature than a bug, however, what the user > pointed out (that MAX_SLAVE is hardcoded instead of staying in conf > file) is quite interesting.
Yes, a limit of 20 slaves is complied into apcupsd. While this is not the way I would have coded it, one must remember that such practices were prevalent at the time apcupsd was written and are quite common today. A limit of 20 is actually reasonable since having more handling more than 20 slaves increases significantly the possibility that the master does not have the time to notify all the slaves before shutdown, particularly if there are network problems due to a router/hub being down due to a power failure. The recommended alternative is to use the NIS networking rather than the Master/Slave networking. This is documented in the manual. There is no limit to the number of NIS "slaves" nor the same problem of notification. If the user would like to submit a patch, and it is written in the current apcupsd style, the apcupsd project will be happy to accept it. Otherwise, this is not an item high on our priority list. I recommend closing the bug report. Best regards, Kern -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
