[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#174004: qmail can't run after update to 2.3.1-6



O.K. Can you add conflict with qmail version <= 1.03-24 please?

Petr Balas


Dne po 23. of December 2002 06:45 sand@celia.serv.net napsal(a):
> This looks like a issue with all of Dan Bernstein's software.  I've
> just seen a similar bug with his "supervise" program in "daemontools"
> (taking down "qmail" and "djbdns", ouch).
>
> The bug appears to be triggered by a change of representation for the
> "errno" variable in the guts of libc6 (from "extern int" to a macro
> around a function call).  When I compile "qmail" against 2.3.1-6 dev,
> it complains about not finding "errno".
>
> According to the glibc Info file:
>
>    ``ISO C specifies `errno' as a "modifiable lvalue" rather than as a
>    variable, permitting it to be implemented as a macro.''
>
> But DJB's code declares it as "extern int errno;" in one of its own
> error files (and doesn't include "<errno.h>", which could macro expand
> the problem away).  So this doesn't seem to be libc's fault.
>
> I'm going to inform Gerrit Pape (maintainer for the unofficial
> pre-compiled DJB .debs) of the problem; I think he'll have to forward
> it upstream as well.
>
> Derek
>
> Petr Balas writes:
> > Package: libc6
> > Version: 2.3.1-6
> >
> > After installing latest libc6 qmail failed to start with "alert: cannot
> > start: unable to read controls".
> > strace qmail-smtpd suggest this is missing configuration file:
> >
> > open("control/percenthack", O_RDONLY|O_NONBLOCK) = -1 ENOENT (No such
> > file or directory)
> > write(0, "alert: cannot start: unable to r"..., 45alert: cannot start:
> > unable to read controls
> > ) = 45
> > _exit(111)                              = ?
> >
> > but this configfile is optional and after downgrading libc6 + locales
> > to 2.3.1-5 all works O.K. Wery strange.
> > Maybe there is some memory corruption in new libc.
> >
> > --
> > Petr Balas (petr at balas dot cz)

-- 
Petr Balas (petr at balas dot cz)



Reply to: