Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 23 Feb 2005 16:13:18 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: ssh-agent and /tmp/ssh-* removal at logout Message-ID: <20050223151318.GO18314@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <421C90CA DOT 2000500 AT kleckner DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <421C90CA.2000500@kleckner.net> User-Agent: Mutt/1.4.2i On Feb 23 06:18, Jim Kleckner wrote: > ssh-agent leaves stale directories named /tmp/ssh-xxxx > that contain the named pipe for authentication. > These left over directories come about when you log out > or shut down the computer without stopping ssh-agent > either by running keychain to shut it down or sending it > a SIGHUP to exit and clean up. > > Could ssh-agent catch the shutdown message and thus > do the proper cleanup? What would that entail? > > Jim > > I noticed that in Karl's script to start keychain: > http://sourceware.org/ml/cygwin/2004-03/msg00167.html > that he removes any /tmp/ssh-* pre-existing and presumed > stale directories left over by dead ssh-agent processes > and this assumes that there is only one ssh-agent per machine. > Not as good as actually getting rid of the source of the > zombie directories. But it's correct behaviour. A forcefully killed process usually isn't in the shape to make cleanup tasks. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/