> > It is a bug introduced at 3.0a6. The conf_cold is always 1.
>
> That seems to be the fix:
>
Yes, it fixes.
But now the previous MX sync problem on Tru64 UNIX shows up again. Is it possible to apply the previous fflush() patch again? Did this patch brake something on other platform?
Here is the extract from the man page of fopen(3) on Tru64 UNIX:
> When you open a file for update, you can perform both input and output
> operations on the resulting stream. However, an output operation cannot be
> directly followed by an input operation without an intervening call to the
> fflush() function or a file-positioning operation (fseek(), fsetpos(), or
> rewind() function). Also, an input operation cannot be directly followed by
> an output operation without an intervening flush or file positioning opera-
> tion, unless the input operation encounters the end of the file.
So between fprintf and fgets an fflush is required in select_protocol(). (extract of the original code):
fprintf(stream, "vers%d\n", vers);
sync_waitdata(s);
if (fgets(line, LINELEN, stream) == NULL) {
There is on spurious fflush() a bit later that is not really needed.
Bests,
AttilaMessage
RE: [milter-greylist] configuration file update
2006-09-20 by attila.bruncsak@itu.int
Attachments
- No local attachments were found for this message.