Anthony Campbell:
> On 19 Dec 2009, Wietse Venema wrote:
> > Anthony Campbell:
> > > > Try:
> > > >
> > > > test -r "$path"
> > > >
> > > > instead of:
> > > >
> > > > test -r $path
> > > >
> > > > does that fix it? If it does, please respond, and attach a compressed
> > > > copy of your postfix-files file. Make sure you are using the right
> > > > postfix-files, with recent releases this is no longer in /etc/postfix,
> > > > look in /usr/lib/postfix/ ($daemon_directory) first.
> > > >
> > > > --
> > >
> > > No difference. I attach two copies of postfix-files; (1) is from
> > > /etc/postfix, (2) is from /usr/lib/postfix.
> > >
> > > Incidentally, I have the same setup on another computer and on that the
> > > error does not appear. I compared the files in the two and couldn't see
> > > any difference. I also purged postfix completely on this machine and
> > > then reinstalled it; still got the error.
> >
> > Then you have a broken /bin/sh program. File a bug report.
> >
> > Wietse
>
> It is bash, which seems to cause no problems on two other machines both
> running postfix so I don't know why it would cause a problem here. I
> reinstalled bash without making any difference.
Clearly, something is different between the machine where the script
breaks, and most if not all other Postfix instances on the planet.
The difference could be
- The script file itself,
- The inputs to the script (including process environment such as
LANG or PATH), (*)
- The /bin/sh program that executes the script,
- Some other file that /bin/sh depends on, such as a library.
I'll look forward to your description of how I would reproduce this
problem (other than you shipping the computers in question to me).
Once there is way to reproduce the problem I can test a solution.
Wietse
(*) Variations in LANG can have dramatic effects on programs
on "system" utilities, for example sort(1).
