On 3/28/2011 8:59 AM, Lima Union wrote:
Hi, while looking in the change log for some info about an issue I'm having[1] I found a simple typo in the date specified as shown here:20200102 Workaround: don't report bogus Berkeley DB close errors as fatal errors. All operations before close are already error checked, so the data is known to be safe. File: util/dict_db.c. Didn't know to how to report this in another way (without 'spamming' the ML). Regards. [1] postfix/verify[3209]: close database /var/lib/postfix/verify_cache.db: No such file or directory
I don't think that is the problem, "20200102" as a date seems a off? -- "All that is necessary for the triumph of evil is that good men do nothing." (Edmund Burke)
