Message-ID: <BAY105-W23B3703F879CBD1726D9C8B5E00@phx.gbl>
From: Karl M <karlm30@hotmail.com>
To: <cygwin@cygwin.com>
Subject: RE: Vista + cygwin basics
Date: Tue, 22 Apr 2008 11:09:17 -0700
In-Reply-To: <480A3B4C.2040205@cwilson.fastmail.fm>
References: <4802CD4D.2030805@cwilson.fastmail.fm>  <480A3B4C.2040205@cwilson.fastmail.fm>
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit


Hi Chuck...

> The other issue is related, I think. I'm using keychain from my
> ~/.bashrc, so it should start an ssh-agent if none is running, and then
> save that PID to a file. Then any new shell can check for the PID in
> that file, contact the exising ssh-agent, and continue.
>
Just a comment...keychain is pretty heavy for what you get in Cygwin. I had problems a long time ago with a slow laptop running XP SP2 with Cygwin windows taking a long time to open if I kicked off several at once, particularly at boot time.

My solution was to launch ssh-agent as a service (one for each user that wants it). That service spawns the agent and updates the user environment in the registry so that other processes can find the ssh-agent process/socket. The advantages are that it is fast and the agent survives a logout (only rekey for a reboot is desired).

I had thought about offering it as a package, but there was insufficient interest. Your are welcome to it if you are interested. It has been rock solid for years.

:.)

...Karl
_________________________________________________________________
Express yourself wherever you are. Mobilize!
http://www.gowindowslive.com/Mobile/Landing/Messenger/Default.aspx?Locale=en-US?ocid=TAG_APRIL

--
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/