Milter-greylist

On Wed, 25 Jan 2006, Emmanuel Dreyfus wrote:

> > I upgraded till milter-greylist 2.1.2 and found that -g flag is already in
> > CFLAGS in makefile. I don't want to run milter-greylist under gdb, because
> > I don't want to stop this process when it will crash.
> Won't any process stop when it crashes?

I use small script which starts greylist again after crash. I don't know
how to start it automatically again under gdb. Another bad thing is that
sometimes greylist works well for two or three days, sometimes it crashes
twice per day. I think that keep gdb running on my server is not very good
thing for server's resources.

For example here my "crash" log for last days:

Fri Jan 20 11:08:24 EET 2006
Fri Jan 20 14:29:30 EET 2006
Fri Jan 20 20:21:25 EET 2006
Mon Jan 23 10:27:59 EET 2006
Mon Jan 23 19:27:36 EET 2006
Tue Jan 24 16:44:13 EET 2006
Wed Jan 25 14:04:07 EET 2006
Wed Jan 25 14:56:23 EET 2006

> > I set no limits to greylist's core but, unfortunally I found that no core
> > dumped after it's crash. Is it possible that greylist do not leave any
> > core files after crash or I missed something?
> It's not on its own to decide that. Maybe it does not have write access to
> its current directory.

Usually i run greylist as smmsp user and from /var/milter-greylist
directory (which is owned by smmsp). But when I got no core with smmsp
user, I started it as "root" but result is still same - no core.

> If it's not a limit issue, then it's a bug...

How can I catch it? Any ideas?

Best Regards, 					mailto:eugenef@...
	Eugene.