Most of what you say I agree: you can't make everybody happy. But perhaps in some minor areas there can be things solved. Two topics:
1) In my opion starts LDAP too late. Not only for amavis. It is such a crucial service. In the way we maintain more complex networks we use LDAP as a crucial source of information for all kind of services. This way we can unify the setup of services like amavis. 2) We use /dev/shm to speed up some services. In the case of amavis we use a subdirectory on /dev/shm to store the temporary files of amavis. For exeample $TEMPBASE="/dev/shm/tmp". If this directory is missing amavis won't start. A solution could be to add such directories to /var/lib/dpkg/statoverride and make the fixdirs() in /etc/init.d/amavis more general. Henrique de Moraes Holschuh schreef: > 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. > > -- Met vriendelijke groet/Regards Prompt R.J. Baart Kerkstraat 173 5261CW Vught tel: +31 73 6567041 mailto:r.j.ba...@prompt.nl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
