Bug 150805 - init script failure
Summary: init script failure
Status: CLOSED DUPLICATE of bug 149657
Alias: None
Product: Fedora
Classification: Fedora
Component: postfix
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-10 19:29 UTC by Thomas Zehetbauer
Modified: 2007-11-30 22:11 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2005-03-18 13:42:51 UTC


Attachments (Terms of Use)

Description Thomas Zehetbauer 2005-03-10 19:29:33 UTC
postfix is perfectly fine using
  alias_database = ${default_database_type}:/etc/postfix/aliases
unfortunately /etc/init.d/postfix insists on running
  postaliases `postconf -h alias_database`
that fails in this configuration. The correct solution is to run newaliases
instead or not try to update the aliases db at all.

Comment 1 Thomas Woerner 2005-03-17 18:59:45 UTC
If you modify your alias database you have to run newaliases afterwards.

Comment 2 Thomas Zehetbauer 2005-03-17 21:24:43 UTC
Correct, one has to run newaliases after modifying the aliases file, so why does
/etc/init.d/postfix insist on it's broken implementation of newaliases?

Comment 3 Thomas Woerner 2005-03-18 11:08:15 UTC
The postalias call is there to check if the alias_database entry is correct: 

- syntactically valid
- file/files existance
- correct permissions
- valid db files

If there is an other way to check this, then I will replace it.


Comment 4 Thomas Zehetbauer 2005-03-18 12:59:39 UTC
alias_database = ${default_database_type}:/etc/postfix/aliases
is syntactically valid but causes the current initscript to fail

aliases_database is AFAIK only used by newaliases, the MTA processes use the
databases defined in alias_maps

postfix runs fine without an alias_database, even without alias_maps

Comment 5 Thomas Woerner 2005-03-18 13:42:51 UTC
Ok, then this bz is the same as #149657.

*** This bug has been marked as a duplicate of 149657 ***


Note You need to log in before you can comment on or make changes to this bug.