On Thu, Oct 03, 2002 at 08:44:29PM -0400, David Humphrey wrote: > Everything looks pretty OK. The message is 'submit'ted, and is seen in > the msgs and msgq directories. But it never moves from there, and any > ESMTP process started up that finds it (or *any* outbound messages) just > sucks down the CPU.
Well there are a couple of things you can try to localise the problem when there is a runaway process. The easiest is to use strace (Linux), ktrace (FreeBSD) or truss (Solaris), which will show you what system calls the process is making. Otherwise you can get the process to dump core (e.g. send a SIGABRT), cd to the source directory, and run gdb -c </path/to/corefile> <program>. Then 'bt' will give a backtrace showing where it was running at the instant it died and the function callback sequence - which you can post to Sam. Actually getting it to create a core file is usually the hard part, especially if it is a non-root process and/or is setuid. I'm not a Linux user; the tricks for FreeBSD are sysctl -a | grep core # set these sysctl variables appropriately and Solaris: mkdir /var/core chmod 1777 /var/core coreadm -p /var/core/%f.%p <process-id> ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
