I'm finding that ssh-agent (launched from my .login) just disappears from my system (Solaris Nevada build 71 on amd64) without apparent provocation.
There are no core files generated (I have coreadm set up to put all core files in a central directory, and I have global setid dumps enabled). There are no log messages generated. It just plain disappears. The only way I notice it is that subsequent invocations of ssh require me to enter my passphrase to unlock my local identity file. It's been doing this for a _long_ time, and through many upgrades, and I guess I've just been hoping the problem would go away with some bug fix. It hasn't. It doesn't happen every time -- I can go through a whole work day without it exiting. It *does* seem to be load-related. (That is, if I do something that really stresses the system, such as ::findleaks on a full kernel dump, then ssh-agent is more likely to depart.) Could this be CR 5004146? I don't see others that are related, and that seems like a stretch. Is there anything I should be doing to debug this? -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
