|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Mike Cappella (lists-general
cappella.us)
Date: Fri Sep 11 2009 - 19:25:36 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 9/11/09 5:05 PM, ghe wrote:
>
> On Sep 11, 2009, at 5:51 PM, Mike Cappella wrote:
>
>>> I don't understand this line from today's logwatch report:
>>>
>>> 308 *Warning: Database file needs update
>>>
>>
>> This message appears when you have a map file that requires
>> postmap'ing to bring the db file up to date relative to the source
>> file. Look at the log messages to see which file is not up to date and
>> run postmap on that file.
>
> Thank's Mike. I found a mention of virtual with google, but since I
> couldn't find the message in /var/log/mail*, I couldn't figure it out.
>
Its in the report at detail >= 5:
$ grep 'older than source' maillog | tail | \
postfix-logwatch --detail 5 --max_report_width=70
****** Summary *******************************************************
10 *Warning: Database file needs update
****** Detail (10) ***************************************************
10 *Warning: Database file needs update ----------------------
9 /etc/postfix/virtual
1 /etc/postfix/transport
> Also since I didn't find it, I just re-postmapped 'em all.
>
No need. The file is indicated in the log and via postfix-logwatch (or
logwatch w/detail >= 5).
Consider using a Makefile to keep source up to date, so that you can
just run "make" w/o thinking about which file needs updating.
--
Mike
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]