Re: [Bug 381269] [NEW] NUT fails to shutdown UPS

2009-07-02 Thread Martin Maney
On Thu, Jul 02, 2009 at 12:47:05PM -, Arnaud Quette wrote: > you're right that the double check is too much, and only due to legacy and > not enough time to make 100 % clean things (that's really a minor point). Actually, what I question is whether the content check is worth doing. But perhap

Re: [Bug 381269] [NEW] NUT fails to shutdown UPS

2009-07-01 Thread Martin Maney
> the solution Martin has proposed can only be considered as a temporary local > fix (ie on your boxes but not for an upload) for affected users, for the > reason I mentioned in the Debian bug linked. Not disagreeing, but frankly I can't see any very great value in the additional check of the flag

[Bug 381269] Re: NUT fails to shutdown UPS

2009-05-31 Thread Martin Maney
I've confirmed that this problem exists in Ibex, not that I really had any doubts. It's been reported to Debian as well, and the maintainer is pondering the best way to repair this for Lenny. I got the impression that this is still in the upstream codebase, so it is to be expected that Jaunty and

[Bug 381269] [NEW] NUT fails to shutdown UPS

2009-05-28 Thread Martin Maney
Public bug reported: Binary package hint: nut It's barely possible that Ubuntu isn't vulnerable to this - I discovered it, and did the actual smoke tests, on a Debian Lenny machine. The problem is that the nut init script's powerdown function relies on calling upsmon -K at a very late point, and

[Bug 289060] Re: named bind9 apparmor profile error

2009-01-04 Thread Martin Maney
Is this ever going to be fixed for the stable release? The repetitive error mesasges about /proc/*/net/if_net6 came to my attention while looking for something else, which led me to this bug. It seems to have been first reported for a version that's still in Ibex, though there's a bumped version