Please keep this on the list so that it gets archived for others to search.
I'm not seeing this problem. I use win-2k and xp machines.
You mentioned that you use a script to launch ssh-agent. I use keychain (also a script to launch ssh-agent) for that. I launch it from a service, so the agent stays aroung from reboot to reboot. If I launch it from within my ~.profile it only stays around for one login session. You also mention that you launch it from profile.d...Is that part of the sysvinit stuff?
I'm attaching the script I use to launch keychain and the script that installs the service with cygrunsrv in case you want to try that. The rm -rf in the launch script keeps the ssh-???? folders from accumulating.
HTH,
...Karl
From: "Andrew J Halls" To: "'Karl M'" Subject: RE: A problem with OpenSSH 3.8.p1-1 - ssh-agent
Date: Wed, 3 Mar 2004 23:44:16 +1030
Hi Karl Turning off McAfee has made no difference.
A couple of additional observations
First the ssh-agent is taking up approx 50% of the cpu while it is running. This is probably all the time it could get from the scheduler and the time the system needs to write to the event log.
Second is that I first noticed this problem after upgrading Cygwin-1.5 dll at around 1.5.3 or 1.5.4 back in September last year.
As I only run one ssh-agent for all by rxvt/bash sessions that I run I use
to run a script, out of /etc/profile.d, that would check to see if there was
a ssh-agent all ready running for the user , if not run one, is so export
the correct SSH_XXXX into the environment if the script could communicate
with that instance else give and error message.
I do this so that I can close all of my rxvt/bash sessions if I needed to
and reattach to the agent later when I started them up again.
What I was noticing was that the first rxvt/bash session started would not
complete it's shutdown until I killed the ssh-agent, this was not the
pervious way the ssh-agent did things before in Cygwin-1.5.1 or 1.5.2 .
This means to me that the ssh-agent was not closing all its file descriptors
properly when going into daemon mode or that the semantics of the fork or
exec call had changed to be more like SVR4.
I have another couple of machines running with Cygwin (the version of the dll has also been upgraded along the way) and OpenSSH-3.7.1p2 on them with the same results at above.
Andy Halls
-----Original Message----- From: Karl M Sent: Wednesday, March 03, 2004 1:21 AM To: [EMAIL PROTECTED] Subject: Re: A problem with OpenSSH 3.8.p1-1 - ssh-agent
Hi...
If you are running McAfee, try turning it off as an experiment. I had ssh socket problems with McAfee in the past.
HTH,
...Karl
>From: Corinna Vinschen >Reply-To: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Subject: Re: A problem with OpenSSH 3.8.p1-1 - ssh-agent >Date: Tue, 2 Mar 2004 11:30:27 +0100 > >On Feb 29 11:19, Andrew J Halls wrote: > > Hi > > I am having a problem with the ssh-agent and excess logging to the > > NT system event logger. After start the ssh-agent over 14,000 log >messages > > are entered into the Application log in less than 60 seconds. Each >message > > content seem to be the same and is as follows: > > > > [...] > > ssh-agent : PID 4672 : error: accept from AUTH_SOCKET: Resource >temporarily > > unavailable. > >This isn't related to the OpenSSH version. I can't tell from the >error message what exactly happened. It doesn't happen on my box. > >Does this happen all the time, reproducibly? If yes, did you try >a recent Cygwin snapshot from http://cygwin.com/snapshots/ if that >cures the problem? > >If not, it would be interesting to see an strace of ssh-agent, perhaps. > > >Corinna > >-- >Corinna Vinschen Please, send mails regarding Cygwin to >Cygwin Developer mailto:[EMAIL PROTECTED] >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/ >
_________________________________________________________________ Get a FREE online computer virus scan from McAfee when you click here. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
_________________________________________________________________
Get business advice and resources to improve your work life, from bCentral. http://special.msn.com/bcentral/loudclear.armx
#!/bin/bash # keychain service # launch keychain from a service so that the ssh-agent survives logoff
# clean up old socket files rm -fr /tmp/ssh-* > /dev/null 2>&1
# launch keychain keychain --noask --quiet
#!/bin/bash # keychain-service-install service-name user-name
if [ "~$1" = "~" ]; then echo No service name exit 1 fi
if [ "~$2" = "~" ]; then echo No user name exit 1 fi
echo Stoping and removing old keychain service cygrunsrv --stop $1 cygrunsrv --remove $1
echo Installing new keychain service cygrunsrv --install $1 \ --args '/bin/keychain-service' \ --dep 'OpenSSH' \ --disp "KeyChain $2" \ --desc "Creates a keychain (ssh-agent) process for $2." \ --path '/bin/bash' \ --user "$2"
echo User $2 requires the Log on as a Service right
-- 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/
