|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Peter H. Coffin (hellsop
ninehells.com)
Date: Thu Jan 31 2008 - 15:54:32 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Jan 25, 2008 at 06:50:19PM -0500, Wietse Venema wrote:
> YOSHIMURA Keitaro:
> > > > I was found a bug.
> > > > "post-install" has forgotten to read data_directory value.
> > > >
> > > > The value of data_directory fails in chown because of emptiness in
> > > > starting the change of post-install of the owner of data_directory.
> > > > Then, processing of post-install stops because of that.
> > >
> > > How are using "post-install". It is not supposed to be invoked directly.
> > There might not be difference in the thing that there is a leakage in
> > the processing when reading from main.cf. Should not this processing be
> > done, and should not I shed it as an error if it should not call it
> > directly?
>
> You MUST NOT invoke the post-install script directly.
I've a similar problem. I just pulled down postfix-2.6-20080127, gave it
my usual make makefiles, built it, and ran make upgrade only. Since this
was overlaying postfix-2.5-20070614, I checked the data_directory
creation.
-----------------
# ls -l /var/lib/
total 8
drwxr-x--- 2 root daemon 512 Jan 26 14:16 dovecot
drwx------ 2 _postfix daemon 512 Jan 31 15:18 postfix
-----------------
I set main.cf to
-----------------
...[rest of main.cf]...
data_directory = /var/lib/postfix
-----------------
Save it and try to start postfix
-----------------
"main.cf" 787L, 30558C written
$ tail main.cf
check_recipient_access pcre:/etc/postfix/recipient_class.pcre
smtpd_data_restrictions =
reject_unauth_pipelining,
reject_multi_recipient_bounce
mime_header_checks = regexp:/etc/postfix/mime_header_checks.regexp
body_checks = regexp:/etc/postfix/body_checks.regexp
body_checks_size_limit = 307200
data_directory = /var/lib/postfix
$ sudo postfix start
postsuper: fatal: bad string length 0 < 1: data_directory =
postfix/postlog: fatal: bad string length 0 < 1: data_directory =
$ tail main.cf
check_recipient_access pcre:/etc/postfix/recipient_class.pcre
smtpd_data_restrictions =
reject_unauth_pipelining,
reject_multi_recipient_bounce
mime_header_checks = regexp:/etc/postfix/mime_header_checks.regexp
body_checks = regexp:/etc/postfix/body_checks.regexp
body_checks_size_limit = 307200
data_directory =
$
-----------------
I go put back the entry for data_directory again, trying with a trailing
slash this time.
-----------------
"main.cf" 787L, 30559C written
$ tail main.cf
check_recipient_access pcre:/etc/postfix/recipient_class.pcre
smtpd_data_restrictions =
reject_unauth_pipelining,
reject_multi_recipient_bounce
mime_header_checks = regexp:/etc/postfix/mime_header_checks.regexp
body_checks = regexp:/etc/postfix/body_checks.regexp
body_checks_size_limit = 307200
data_directory = /var/lib/postfix/
$ sudo postfix start
postsuper: fatal: bad string length 0 < 1: data_directory =
postfix/postlog: fatal: bad string length 0 < 1: data_directory =
$ tail main.cf
check_recipient_access pcre:/etc/postfix/recipient_class.pcre
smtpd_data_restrictions =
reject_unauth_pipelining,
reject_multi_recipient_bounce
mime_header_checks = regexp:/etc/postfix/mime_header_checks.regexp
body_checks = regexp:/etc/postfix/body_checks.regexp
body_checks_size_limit = 307200
data_directory =
$
-----------------
I'm not sure, but it LOOKS like the postfix start is first wiping out
the data_directory = value, and then complaining that it doesn't have a
value long enough.
Any recommendations, or suggestions as to what information might be
useful?
--
It's not hard, it's just asking for a visit by the fuckup fairy.
-- Peter da Silva
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]