attila.bruncsak@... wrote:
>
> > >
> > http://lists.freebsd.org/pipermail/freebsd-bugs/2005-January/0
> > 11028.html
> >
> > That message contains a workaround. If calls fclose() on
> > the FILE*, then immediately uses dup2() to re-allocate the
> > file descriptor low_fd.
> >
>
> It is not guaranteed in a multithreaded program working reliably.
Come on, multithreaded programming isn't voodoo magic. :-)
You can easily make the guarantee that there is no race
condition by properly programming, e.g. using a semaphore
or mutex. If you're doing threaded programming, then you
should very well know what you're doing anyway.
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, Gesch\ufffdftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M\ufffdn-
chen, HRB 125758, Gesch\ufffdftsf\ufffdhrer: Maik Bachmann, Olaf Erb, Ralf Gebhart
FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd
"Perl will consistently give you what you want,
unless what you want is consistency."
-- Larry WallMessage
Re: [milter-greylist] peering problems on sun 8
2007-03-09 by Oliver Fromme
Attachments
- No local attachments were found for this message.