The patch below fixes many errors of the form:
*** WARNING: line containing nothing but whitespace in paragraph at line 37
in file writing.pod
*** WARNING: line containing nothing but whitespace in paragraph at line 40
in file writing.pod
There are also a couple of minor typo-fixes.
On Jun 2, 2009, at 16:10, Ask Bjørn Hansen wrote:
With all the recent prefork fixes it seemed like a good idea to make
another release, so:
http://smtpd.develooper.com/get.html
Oh, and if it hasn't been obvious from the list posts, this release is
entirely thanks to Charlie, Norman and
With all the recent prefork fixes it seemed like a good idea to make
another release, so:
http://smtpd.develooper.com/get.html
:-)
- ask
0.82 - June 2, 2009
prefork: Fix problem with processes sometimes being "left
behind" (Charlie Brady)
prefork: Fix startup when no interfa
Jared Johnson wrote:
Why not set --idle-children at start-up to something higher (or just 0
to disable)?
Setting it higher is a bit bothersome because our QP children use too
much memory right now (mainly from using DBIx::Class), so it would be a
bit unfortunate to have more memory-consuming
Why not set --idle-children at start-up to something higher (or just 0
to disable)?
Setting it higher is a bit bothersome because our QP children use too
much memory right now (mainly from using DBIx::Class), so it would be a
bit unfortunate to have more memory-consuming kids around that aren'
Diego d'Ambra wrote:
[...]
But you're right, there is also code in the reaper function - remove the
array of children terminated, hmmm... I think we should delete that.
This can't be deleted - parent is using this to track children, clean-up
and possible reset of shared memory.
--
Best r
Robert Spier wrote:
Diego d'Ambra wrote:
Charlie Brady wrote:
On Fri, 29 May 2009, Diego d'Ambra wrote:
[...]
Latest version of prefork also handles a possible race better, the
parent will detect a lock and reset shared memory.
Sorry, I've to correct myself, that's not true. Apparently my
p
Jared Johnson wrote:
Even if you're not near max children the parent will only spawn max idle
children, then it sleeps until an event, wake-up and see if more
children are needed. Debug log should give some clue, if this is the
reason.
Bingo. Looking further into things, it was apparent that a
> Here's where the bug is:
>
> if ($detach) {
> open STDIN, '/dev/null' or die "/dev/null: $!";
> open STDOUT, '>/dev/null' or die "/dev/null: $!";
> open STDERR, '>&STDOUT' or die "open(stderr): $!";
> defined (my $pid = fork) or die "fork: $!";
>
