Bug#606317: apache2: upgrade to sysvinit causes apache virtualhosts to fail - started before bind9

2011-01-06 Thread Thomas Goirand
On 01/06/2011 08:17 AM, christ...@hilbert.alphasky.net wrote: > Thomas Goirand wrote: > >> Hi Ian, >> >> I think that if nobody found the issue, it's because nowadays, almost >> everyone is using IP based virtualhosts, because starting apache with >> named virtualhost makes apache resolve as many

Bug#606317: apache2: upgrade to sysvinit causes apache virtualhosts to fail - started before bind9

2011-01-05 Thread christoph
Thomas Goirand wrote: > Hi Ian, > > I think that if nobody found the issue, it's because nowadays, almost > everyone is using IP based virtualhosts, because starting apache with > named virtualhost makes apache resolve as many hostname as you have > vhosts, and in many situations, this can take a

Bug#606317: apache2: upgrade to sysvinit causes apache virtualhosts to fail - started before bind9

2011-01-02 Thread Thomas Goirand
Hi Ian, I think that if nobody found the issue, it's because nowadays, almost everyone is using IP based virtualhosts, because starting apache with named virtualhost makes apache resolve as many hostname as you have vhosts, and in many situations, this can take a long long time. Anyway, did you t

Bug#606317: apache2: upgrade to sysvinit causes apache virtualhosts to fail - started before bind9

2010-12-08 Thread Ian Jeffray
Package: apache2.2-common Version: 2.2.16-4 Severity: normal Can't believe nobody else has hit this before, but can't see it in the bug tracker. The new dependency-based init scheme added in debian testing has caused apache2 to be started before bind9. This means that it can't resolve hostname