Timestamps for configuration files are not kept (causes warnings after Postfix update)

Solution Verified - Updated -

Issue

  • By default all timestamps of /etc/postfix/* are the timestamps of "make install" when the RPM package is built. While this is not an issue in general, this may cause warnings after a postfix update in a common scenario like this:

  • Have /etc/postfix/virtual empty (like the default), but reference it within main.cf. This needs a "postmap /etc/postfix/virtual" indeed. Everything fine so far. Then a postfix update happens, /etc/postfix/virtual gets replaced by the newer file from the RPM package - which leads to a newer timestamp. This however makes postfix complaining in logs: "postfix/smtpd[11483]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual". The main point here, is that the content of virtual nor virtual.db changed, just the timestamp of the "source" file.

  • This issue could be avoided if "install -p" rather "install" is used or if there is a "touch -c -r " within the spec file. If there is any upstream change of one of these files, the newer filestamp would indeed be applied and thus causes a *.rpmnew (if the original file was touched) - as it's expected further on.

Environment

  • postfix-3.0.3-5.fc24
  • Red Hat Enterprise Linux 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In