Subject: Tracking down a core?
To: None <netbsd-users@netbsd.org>
From: Christopher W. Richardson <cwr@nexthop.com>
List: netbsd-users
Date: 05/16/2005 11:21:18
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

For some time now, I've been noticing that when I come into work
after I've been out of town for a while, or even over a weekend,
I find xlock is not running on my workstation.  For a while I had
thought this was just stupidity on my part, and that I was
forgetting to set it when I left the office.  However, the
frequency has grown such that I no longer believe this is the
case, and suspect that something else is going on.

Checking in authlog, I don't see any indication that
administrators have been coming by and logging in as root, so I'm
left thinking that the process is crashing if left running for
some unknown amount of time > 12-14 hours (I don't normally find
this when I leave in the evening and come back the next
morning).  However, I can't find a core file anywhere on the
system.

This is with 2.0.2_STABLE i386 (built with xsrc from the same
time) with a custom kernel as of a few days ago (but, if I'm
right, has been going on for quite a while, perhaps since 2.0).
Here is the relevant data:

cwr@achilles#pkg_info -a | grep -i xlock
xlockmore-5.16      Like the XLock session-locker/screensaver, but with more
r@achilles#sysctl -a | grep -i core
kern.defcorename = %n.core
proc.curproc.corename = %n.core
proc.curproc.rlimit.coredumpsize.soft = unlimited
proc.curproc.rlimit.coredumpsize.hard = unlimited

The only thing resembling an error which I can find is the
following on xconsole:

X Error of failed request:  BadPixmap (invalid Pixmap parameter)
  Major opcode of failed request:  56 (X_ChangeGC)
  Resource id in failed request:  0x0
  Serial number of failed request:  680172694
  Current serial number in output stream:  680172700

However, as it doesn't provide an application name, or a
timestamp, I don't really know if this is even related.

Does anyone have any suggestions how to track down where my xlock
is going?

TIA,
Chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFCiLpsP65RBOOHTzERAhKEAJ9NUYRux8qchIhYbbai0+rqgkUStACfQNZa
+V0i0/s3FcakTGYrv9w7AEk=
=d+Kr
-----END PGP SIGNATURE-----