On Sat, 03 Oct 2009, Paul Traina wrote: > I did look at the docs before sending in the fragment. In no place > in the LSB documentation does remote_fs imply that local_fs has > already happened, so technically, having both is a good thing. Many
So, we list both. > >Do we need clamav-daemon in there? I don't object to the other > >deps, but > >clamav-daemon really shouldn't need to be started before amavisd- > >new... > > Again, it's a windowing problem. Amavisd-new technically doesn't > need to be started before the MTA, but the services should be in > place. If clamav-daemon isn't around, we may or may not fall back > to clamscan, but amavis is looking to connect to the control socket No fallback to clamscan is considered an unsupported configuration, but I have no strong feelings about this dependency. > >>Again, it shouldn't break things that don't have any of the "should" > >>severs (or do). > > > >Did you test it? > > Extensively, under my environment, which is postfix+amavis+clamav > +spamassassin but not using LDAP or MYSQL for amavis-purposes (but > having MYSQL on the machine for other reasons and no LDAP at all). > This should give us reasonable coverage. Yes. One last corner case: please add a dependency to a service amavisd-new does _NOT_ need to work, and make that service *fail* to start (with a non-zero status code). amavisd-new must still attempt to start. Does that happen? -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
