On Sat, Apr 19, 2003 at 10:22:45 +1000, Brian May wrote: > On Fri, Apr 18, 2003 at 09:33:01PM +0200, [EMAIL PROTECTED] wrote: > > Package: amavisd-new > > Version: 20021227p2-5 > > Severity: grave > > Grave would seem to be a bit of an overkill? amavisd-new still works OK > for the majority of users... >
I chose grave, because in the state described below one of the amavisd ate 100% cpu constantly (this was how I noticed the problem). > > when > > - amavis-ng is installed (I used version 0.1.6.2-1), > > - and amavisd-new previously had been installed but now only its > > config-files are present, > > then > > the init-scripts of _both_ packages start the program > > /usr/sbin/amavisd > > I really don't know what to do about this bug. I think the > same thing has happened before with similar situations, but > I don't know what was decided. > > Both init-scripts check for the existance of /usr/sbin/amavisd, > and assume it is their version of the program and will run it. yes. So maybe one of the packages should have its amavisd renamed. -- Ernst Kloppenburg Stuttgart, Germany