I instrumented a kernel so I could find out who was setting the coredump size to zero so that core dumps are disabled under SLP 9.0 i386. The culpruit was a very big surprise and I ask for anyone's help in telling me what role gpg-agent plays in KDM startup. I modified sys_setrlimit() in /usr/src/linux-2.4.21-166/kernel/sys.c to print out the process name, pid and parent pid of a process tries to set the core dump size to zero via: if ((resource == RLIMIT_CORE) && (rlim->rlim_max == 0)) { printk("process %-13.13s pid %d ppid %d setrlimit(RLIMIT_CORE, 0)\n", current->comm, current->pid, current->p_pptr->pid); } What I got was a big surprise. In /var/log/messages: Jan 20 14:50:44 jutopia kernel: process gpg-agent pid 2381 ppid 2334 setrlimit(RLIMIT_CORE, 0) The parent of gpg-agent is KDM (determined by ls -l /proc/2334/exe point as a symlink to /opt/kde3/bin/kdm). I don't see where it is called in /opt/kde3/share/config/kdm/*. It does however exec(2) over itself and is running as "/bin/sh /usr/X11R6/bin/kde". Does anyone have an idea why gpg-agent is part of a KDM log on? Thanks. -- _/_/_/ Bob Pearson gottadoit@mailsnare.net _/_/_/ "The best way to get information on Usenet is not to ask a _/_/_/ question, but to post the wrong information." - Aahz' Law