2008/4/14, Arjen de Korte <[EMAIL PROTECTED]>: > >> I think that is the best thing to do. So I'll just remove the alarm() > >> mechanism from the clients, since that's become obsolete now that we > >> have non-blocking read/write that provides a much cleaner interface. > > ok > > I'm preparing -pre2. Is it ok for you? > > > Yes. I found that the only client that is using alarm to break out of > stalled read/write actions is upsmon. Since having alarms doesn't hurt > (they are just redundant now), we can probably leave them in for now. So > go ahead, release -pre2.
done 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-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
