manu@... wrote: > Eugene Filatov wrote: > > > I have another simple idea - just replace "exit()" with "return" in this > > function. So greylist will just skip dumping and inform about it via > > syslog but it will continue to work. > > > > Emmanuel, what do you think about it? > > I'm not sure it's acceptable for the average administrator: if you don't > check the logs, you get toasted when milter-greylist restarts because it > never dumped its database. > > Perhaps we could figure a way of booking a FILE *? Sorry I don't remember exactly what the actual problem is, but ... Shouldn't it be sufficient to open() the dump file right from the start and never close() it? Only always write to it, then fsync()+lseek(0). (And fflush()+rewind() if stdio functions are used to write the file.) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.
Message
Re: [milter-greylist] milter-greylist-2.0.2 crash
2006-07-27 by Oliver Fromme
Attachments
- No local attachments were found for this message.