Hmm, I have "child is killed by force", but rarely. And I'm not sure this is what's cousing the problem.
Today I also have few zero byte files, bet no errors, no kills in logfile.
And it always logs "injecting / removed" message pair for each id.

About lmtp or smtp, my clapf config file doesnt have this option ;)
Postfix is accepting smtp.


/Toms

----- Original Message ----- From: <s...@datanet.hu>
To: "Toms Trankalis" <toms.tranka...@telia.lv>
Cc: <clapf-users@lists.acts.hu>
Sent: Wednesday, October 10, 2007 11:04 AM
Subject: Re: [clapf-users]


Hello Toms,

I am glad to hear that clapf is running fine. Could you please show me
the syslog messages concerning the id (ie. name) of a zero length file
to see what is happening? Normally, clapf should remove its queue file
after it has done with it.

Have you noticed a "child is killed by force" messages in the syslog,
and what local delivery method do you use (lmtp or smtp)?

On Wed, 10 Oct 2007, Toms Trankalis wrote:

By now, clapf ir running fine on my mail gateway, but...
noticed the following problem using ramdrive.

It appears, that when clapf delivers message, sometimes it leaves zero byte file in temp dir.
So after some time, about a week or 2, i run out of inodes on ramdrive ;)

What could cause this?


/Toms




Digitally yours,

SJ.

--





Reply via email to