Re: postmulti fatal error with 3.0.0

2015-02-18 Thread Wietse Venema
Andreas: > Am 2/18/2015 um 18:39 schrieb Viktor Dukhovni: > > With 3.0.0 Linux distributions should start using the upstream > > default. This does mean that users should remove explicit legacy > > default settings of daemon_directory from their main.cf files. > > Distribution package upgrades will

Re: postmulti fatal error with 3.0.0

2015-02-18 Thread li...@rhsoft.net
Am 18.02.2015 um 19:59 schrieb Andreas: Am 2/18/2015 um 18:39 schrieb Viktor Dukhovni: With 3.0.0 Linux distributions should start using the upstream default. This does mean that users should remove explicit legacy default settings of daemon_directory from their main.cf files. Distribution pac

Re: postmulti fatal error with 3.0.0

2015-02-18 Thread Andreas
Am 2/18/2015 um 18:39 schrieb Viktor Dukhovni: > With 3.0.0 Linux distributions should start using the upstream > default. This does mean that users should remove explicit legacy > default settings of daemon_directory from their main.cf files. > Distribution package upgrades will need to update or

Re: postmulti fatal error with 3.0.0

2015-02-18 Thread Wietse Venema
Viktor Dukhovni: > The upstream Postfix release defaults to > > daemon_directory = /usr/libexec/postfix > > on all but one system type (GNU0 Debian whatever that is), > and even that one should probably be changed to /usr/libexec. Postfix should have its own libexec subdirectory. Unlike comm

Re: postmulti fatal error with 3.0.0

2015-02-18 Thread Viktor Dukhovni
On Wed, Feb 18, 2015 at 11:16:19AM +0100, Andreas wrote: > > This is something the distribution maintainers will have to figure > > out. If you are a distribution maintainer, please DO NOT apply > > the above patch unless it is first adopted upstream. > > Since, as you said, some distributions la

Re: postmulti fatal error with 3.0.0

2015-02-18 Thread Wietse Venema
Andreas: > Since, as you said, some distributions lack /usr/libexec, wouldn't > it be a better idea to leave it up to the package/distribution > maintainers to separate shared objects from shared executables? That is not how Postfix works. With Postfix, things are forbidden unless explicitly permi

Re: postmulti fatal error with 3.0.0

2015-02-18 Thread Andreas
Dear Viktor, sorry, i got your mail quite delayed... i can confirm this patch working, thank you! > IIRC the main reason for the conflict detection in question is to > avoid use of the shared directories also as per-instance directories. Which is a very good idea and prevents many configuration e

Re: postmulti fatal error with 3.0.0

2015-02-17 Thread Viktor Dukhovni
On Wed, Feb 18, 2015 at 02:11:34AM +0100, Andreas wrote: > On many systems (Debian, Arch, and probably more) daemon_directory is > /usr/lib/postfix as well, which will lead to a broken multi-instance > capability by default. Note that on BSD systems daemon_directory is /usr/libexec, and Linux FHS

Re: postmulti fatal error with 3.0.0

2015-02-17 Thread Andreas
Yes, this is what the error tells me, but is there any reason behind this? In the documentation i couldn't find any hint, why this should be a bad idea. Also i did not set this explicitly, but shlib_directory by default will be /usr/lib/postfix if compiled with shared=yes On many systems (Debian,

Re: postmulti fatal error with 3.0.0

2015-02-17 Thread Viktor Dukhovni
On Tue, Feb 17, 2015 at 07:32:22PM -0500, Wietse Venema wrote: > > > # postmulti -l > > > postmulti: fatal: instance /etc/postfix, > > > shlib_directory=/usr/lib/postfix conflicts with instance /etc/postfix, > > > daemon_directory=/usr/lib/postfix > > DO NOT set daemon_directory the same as shli

Re: postmulti fatal error with 3.0.0

2015-02-17 Thread Wietse Venema
Andreas: > Hi, > > i installed the new postfix-3.0.0 in my arch system, however by default > (default main.cf ) postmulti results in a fatal error > for a reason (conflict) i don't understand: > > > # postmulti -l > > postmulti: fatal: instance /etc/postfix, > > shlib_directory=/u