On 15/3/2012 12:46 μμ, Nikolaos Milas wrote:
Subsequently, build was successful!
I used:
AUXLIBS="${AUXLIBS} -L/usr/local/openldap/lib64 -lldap -llber"
I've found that building Postfix RPMs like this, does NOT use the simple
ldap library symlinks; in fact it uses:
# ldd /usr/sbin/postf
Sahil Tandon:
> > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter:
> > var_flock_tries=40
> > ...
> > I guess that the "var_flock_tries" parameter (which I had added
> > according to:
> > http://tech.groups.yahoo.com/group/postfix-users/message/277428)
> > might not be availabl
On Sat, 2012-03-17 at 16:46:24 +0200, Nikolaos Milas wrote:
> ...
> /usr/sbin/postconf: warning: /etc/postfix/master.cf: unused
> ...
> "fallback_relay parameter has been removed" is no more available in v2.9 ?
% grep -A 2 fallback_relay RELEASE_NOTES-2.3
[Incompat 20051208] The fallback_relay
On 16/3/2012 11:21 πμ, Nikolaos Milas wrote:
I'll test this hypothesis anyway, but it's good to know others'
experience on such matters.
So, I've upgraded on a test server with a vanilla postfix (standard
settings, as installed on CentOS 5, i.e. ) which had been upgraded in
the past to 2.8.2
On 15/3/2012 11:30 μμ, Wietse Venema wrote:
One set of config files will produce the same result ONLY if you
use it with the same Postfix version.
...
Postfix actually updates config files so that they keep producing the same
result as with your older Postfix version, to the extent that this
Nikolaos Milas:
> > If you just copy old config files over a new Postfix installation
> > then you will end up with a broken system.
>
> Hmm, could you please provide some more details on it? Why so? I would
> imagine that a full set of master.cf, main.cf and any other files used
> therein (hash
On 15/3/2012 7:56 μμ, Nikolaos Milas wrote:
So, I guess that if I upgrade using an RPM (through "rpm -Uvh"), as I
described, the upgrade is expected to be successful too?
I would like to also clarify that the system shows:
# rpm -qa | grep postfix
postfix-2.3.3-2.1.el5_2
because the s
On 15/3/2012 4:01 μμ, Wietse Venema wrote:
Instead, use "make upgrade" which updates main.cf and master.cf
to maintain compatibility with the earlier version.
Thank you Wietse.
That's how I've been upgrading until now (using "make upgrade"). But now
I want to switch from source-compilation t
Nikolaos Milas:
> Is there a way to completely uninstall this version?
That would be a mistake - you'd lose your configuration.
Instead, use "make upgrade" which updates main.cf and master.cf
to maintain compatibility with the earlier version.
If you just copy old config files over a new Postfix
On 15/3/2012 12:46 μμ, Nikolaos Milas wrote:
Now I'll have to setup an installation to test everything and confirm
correct software operation.
I would like to test the new RPMs on a server (CentOS 5.8 x86_64) where
there is already a Postfix v2.8.2 built from source (following
directions:
On 15/3/2012 3:14 πμ, Sahil Tandon wrote:
Does your /etc/ld.so.conf contain the
appropriate paths, and is your hints file up to date?
Thank you Sahil,
Your hint gave me a solution:
I found that there was no ld path configured for these libraries.
I created a file: /etc/ld.so.conf.d/openldap
On Thu, 2012-03-15 at 02:08:15 +0200, Nikolaos Milas wrote:
> On 15/3/2012 1:54 πμ, Sahil Tandon wrote:
>
> >/usr/local/openldap/lib != /usr/local/openldap/lib64
>
> I know; I am wondering whether this is the problem.
> ...
> My first try used precisely "/usr/local/openldap/lib64" and build
> fa
On 15/3/2012 1:54 πμ, Sahil Tandon wrote:
/usr/local/openldap/lib != /usr/local/openldap/lib64
I know; I am wondering whether this is the problem.
I think that the build process uses 64 bit libs correctly when needed
and produces automatically both 32 bit and 64 bit RPMs if the required
lib
On Thu, 2012-03-15 at 01:45:43 +0200, Nikolaos Milas wrote:
> ...
>%if %{with_ldap}
> CCARGS="${CCARGS} -DHAS_LDAP -I/usr/local/openldap/include"
> AUXLIBS="${AUXLIBS} -L/usr/local/openldap/lib -lldap -llber"
>%endif
>
> ...
> However, I see that at the end of the build proces
On 13/3/2012 7:58 μμ, Nikolaos Milas wrote:
As far as I know, most people creating RHEL Postfix RPMs are using S.
J. Mudd's src.rpm but I don't know if someone has extended the
included spec files to support custom LDAP paths.
I have been able to use S. J. Mudd's src.rpm to build RPM packages
On 13/3/2012 7:20 μμ, Quanah Gibson-Mount wrote:
I do the following as part of CCARGS to postfix:
Thank you Quanah,
Your post certainly provides valuable info regarding building from source.
I am now mainly trying to research how to pass the paths through a spec
file... (I have been buildin
--On Tuesday, March 13, 2012 6:46 PM +0200 Nikolaos Milas
wrote:
Hello,
Now, how can we specify custom paths to LDAP libraries, header files,
etc. in the spec file ?
I do the following as part of CCARGS to postfix:
-DHAS_LDAP -DHAS_MYSQL -DUSE_TLS $(DBINC) $(PCRE_DEF)
$(PCRE_INCLUD
Hello,
This is a question to people who have some experience in building
Postfix RPMs.
I am trying to build Postfix RPMs for RHEL/CentOS 5 x86_64. These RPMs
should have standard options (those that are included in the standard
CentOS Postfix RPM).
The idea is to use
http://ftp.wl0.org/of
18 matches
Mail list logo
