X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
From: "Mark Moriarty" <mfmori AT hotmail DOT com>
To: "'Karl M'" <karlm30 AT hotmail DOT com>, <cygwin AT cygwin DOT com>
References: <4802CD4D DOT 2030805 AT cwilson DOT fastmail DOT fm>  <480A3B4C DOT 2040205 AT cwilson DOT fastmail DOT fm> <BAY105-W23B3703F879CBD1726D9C8B5E00 AT phx DOT gbl>
Subject: RE: Vista + cygwin basics
Date: Tue, 22 Apr 2008 19:25:57 -0400
Message-ID: <019801c8a4d0$37d66750$3202a8c0@Mark>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <BAY105-W23B3703F879CBD1726D9C8B5E00@phx.gbl>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

I'd be interested in it :) 

-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of
Karl M
Sent: Tuesday, April 22, 2008 2:09 PM
To: cygwin AT cygwin DOT com
Subject: RE: Vista + cygwin basics


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/




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