On Fri, 20 Mar 2009, Ruud Baart wrote: > It is a bug on several system we maintain. As far as I can trace it must be > related to
We'd need initscripts facilities for ldap, sql-database, etc. And to depend on those, to do it properly. And to have the relevant packages providing these facilities in their initscripts. Maybe depending on all of the commonly used packages to provide such stuff would work. IF you're using upstart to do dependency-based boot ordering. And it will be damn ugly :( Especially for setups that don't require it. Other than that, the only thing we can do is push amavisd-new to order 99 and if anything else it wants in your particular config is at order 99, you lose. But that will, of course, break setups that want stuff to start after amavisd-new. I am NOT against it, mind you. The only setup I consider sane is dual-MTA, and that always work fine if amavisd-new starts last. > Amavis can depends on LDAP, postgres, clamav and other services. I assume it > starts > too early and therefor fails. In our setup Amavis depends on LDAP, postgres > (through dspam) > and clamav. It doesn't depend on clamav unless you did something really busted in your configuration. It will either run clamscan until clamd is ready, or wait for clamd. It will _not_ fail to start because of clamav. -- "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
