Actually, I was thinking more of a change in the way a kernel function behaves. However, never having looked at the NUT code, I defer to anyone who has. I agree that the -D flag on the kernel routine "should" only affect timing.
FWIW, the discussion at: http://osdir.com/ml/monitoring.nut.devel/2008-01/msg00038.html may be relevant. Dave On Wed, Jan 12, 2011 at 10:13 PM, Charles Lepple <[email protected]> wrote: > On Jan 12, 2011, at 11:16 AM, Knight, Dave wrote: > > My guess would be that there is some miscommunication between driver >> levels, perhaps a result of running a new nut with an old kernel (latest is >> 2.6-37)? >> > > There is not much in NUT which would depend on new kernel features, > especially when the problem is masked by enabling debug output on that same > kernel version. (The debug flag shouldn't affect anything but timing, as far > as USB is concerned.) > -- "Ridicule is man's most potent weapon. It’s hard to counterattack ridicule, and it infuriates the opposition, which then reacts to your advantage." Saul Alinsky, Marxist, Obama mentor
_______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
