To apply this patch, cd into the Postfix-2.5.* top-level source
directory and execute:
$ patch thismessage
We were able to reproduce the scheduler looping problem, and it
does not recur with the patched version
A question ... what' the way to make this patch to be included in
Ubuntu
On Fri, 06 Mar 2009 10:07:26 +0100
Santiago Romero srom...@servicom2000.com wrote:
A question ... what' the way to make this patch to be included in
Ubuntu Server postfix packages?
I mean, should I submit your message+patch to the package maintainers
of Ubuntu / Debian / Redhat so that new
Gerard escribió:
In a perfect world, the program maintainers would know about the patch
and take steps to correct their package/port or whatever. You might
want to contact the maintainer of Postfix for your Distro and see if
they are planning on updating the package/port. Usually, they do get a
Santiago Romero:
To apply this patch, cd into the Postfix-2.5.* top-level source
directory and execute:
$ patch thismessage
We were able to reproduce the scheduler looping problem, and it
does not recur with the patched version
A question ... what' the way to make this patch to
Wietse Venema wrote:
You might want to repeat your precise Postfix version at this point,
and which queue manager version is configured in your master.cf.
Current Postfix versions have (qmgr=new, oqmgr=old) in master.cf.
Older Postfix versions have (nqmgr=new, qmgr=old) instead. The
Santiago Romero:
(I mean, setting rate_ values higher or lower so that the problem
reproduces again faster, because it passed 5 days between the last 2
times qmgr ate the CPU...).
Just run the same test.
Thanks,
Wietse
On Thu, Mar 05, 2009 at 12:20:06PM +0100, Santiago Romero wrote:
Well, I'm using postfix's ubuntu package, so it's not compiled from source
code because I need all my ~=100 Linux machines to be easily updatable
(apt-get update apt-get upgrade).
In this case, I'm going to recompile .deb
Please wait for an updated patch, we believe we have identified the
cause and reproduced the symptoms (in that order). I have a candidate
patch, but I expect Wietse will send an updated more polished version
in the not too distant future.
Ok, I'll wait for it. I'm going to roll back to
On Thu, Mar 05, 2009 at 04:21:01PM +0100, Santiago Romero wrote:
Please wait for an updated patch, we believe we have identified the
cause and reproduced the symptoms (in that order). I have a candidate
patch, but I expect Wietse will send an updated more polished version
in the not too
Santiago Romero:
Please wait for an updated patch, we believe we have identified the
cause and reproduced the symptoms (in that order). I have a candidate
patch, but I expect Wietse will send an updated more polished version
in the not too distant future.
Ok, I'll wait for it.
On Thu, 5 Mar 2009 13:03:11 -0500 (EST)
wie...@porcupine.org (Wietse Venema) wrote:
It will be later today. I don't have much time so I want to have
it really right the first time. Code that is right takes more work
than code that works.
Reminds me of a plaque I have in my office.
There
Wietse Venema:
Santiago Romero:
Please wait for an updated patch, we believe we have identified the
cause and reproduced the symptoms (in that order). I have a candidate
patch, but I expect Wietse will send an updated more polished version
in the not too distant future.
12 matches
Mail list logo
