Darren J Moffat writes: > James Carlson wrote: > > 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. > > So we need to "trap" its exit and find out how what is causing it to > exit "apparently" cleanly. > > It exists on SIGTERM (which is what ssh-agent -k actually does).
I very much doubt that anything I'm doing would send it SIGTERM, but I can start debugging. > > 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. > > Good for you then that you are doing it from .login rather than using > gdm because ssh-agent "disappearing" would cause the whole session to > logout (since gdm runs the session "under" ssh-agent). Yikes. > > 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? > > It if is 5004146 you should be able to verify, using DTrace, and looking > to see if ssh-agent has died just after getting a request. OK. I was mostly fishing to see if anyone else has seen this or if (maybe) I'm the only one trying to use ssh-agent. ;-} -- 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
