> > Was there any incompatible changes which I am not aware of? > > Or it should just work as before and there is a bug on that > platform? > > > A quick fix for you would be to configure --sysconfdir=/etc > --localstatedir=/var > > Here is the long story: > > The previous configure script forced --sysconfdir=/etc > --localstatedir=/var Thanks for the detailed information, I will add this to my site specific configure script. > > This oddity has been "fixed", with the result of a bare configure > producing a milter-greylist that look in /usr/local/etc/mail and > /usr/local/var/milter-greylist. > > There is a backward compatibility check for a config file in > /etc, hence > the rough warning you get. The same test was forgotten for the dump > file, which should not be a problem, as loosing the database > just cause > extra delay. Would be great to add the checking code. The result is more than a simple extra delay, milter-greylist is exiting with EX_OSERR. > > What is really surprising here is that make install did not create > /usr/local/var/milter-greylist (the install-db rule should do it). > > What does make install produces at yours? > There is no surprise here, I am not running "make install" at all. I am just copying the new milter-greylist binary through our firewall from the internal development system to the external production mail perimeter system. Bests, Attila
Message
RE: [milter-greylist] Issue with upgrading mg on Tru64 UNIX from 4.3.2 to 4.3.4
2009-12-11 by attila.bruncsak@itu.int
Attachments
- No local attachments were found for this message.