On Wed, Jan 25, 2006 at 02:03:22PM +0200, Eugene Filatov 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 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. > Current limits for greylist: > plimit 20180 > 20180: /usr/local/bin/milter-greylist > resource current maximum > time(seconds) unlimited unlimited > file(blocks) unlimited unlimited > data(kbytes) unlimited unlimited > stack(kbytes) 8192 unlimited > coredump(blocks) unlimited unlimited > nofiles(descriptors) 2048 2048 > vmemory(kbytes) unlimited unlimited If it's not a limit issue, then it's a bug... -- Emmanuel Dreyfus manu@...
Message
Re: [milter-greylist] milter-greylist-2.0.2 crash
2006-01-25 by Emmanuel Dreyfus
Attachments
- No local attachments were found for this message.