git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Faye-Lund <kusmabite@gmail.com>
To: GAURAV BAHL <engg.bahl@gmail.com>
Cc: msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: [msysGit] GIT connect "connect to host HOSTNAME port 22: Bad file number" message shown
Date: Wed, 1 Dec 2010 14:33:27 +0100	[thread overview]
Message-ID: <AANLkTi=tm9wX08_o2xgmSS371atgsfPqydT-AZLYxNwJ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=GnOJvZE1hGcCbRq9G8KrqnM2ULXZXRCAP-Gpv@mail.gmail.com>

On Wed, Dec 1, 2010 at 1:48 PM, GAURAV BAHL <engg.bahl@gmail.com> wrote:
>
> My Manager asked me sent it out c/Documents and Settings
> Administrator/.ssh/id_rsa.pub file to someone for adding so that git should
> be available to me.
> Once done with the approval , I tried with above command and faced Bad file
> name issue
>
> Let me know for more Infn.
>
> After addition of the key the GIT bash Testing connection using (ssh
> git@HOSTNAME info) command outputs as
>
> gaurav.bahl@008_GAURAVB ~
> $ ssh git@HOSTNAME info
> ssh: connect to host HOSTNAME port 22: Bad file number
>

You probably need to replace "HOSTNAME" with the host name of the
server you want to test the connection against.

  reply	other threads:[~2010-12-01 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 12:48 GIT connect "connect to host HOSTNAME port 22: Bad file number" message shown GAURAV BAHL
2010-12-01 13:33 ` Erik Faye-Lund [this message]
     [not found]   ` <AANLkTimCgHwXfYJveFFKK3JEa6j3rieeQMzxxHzFVZ9f@mail.gmail.com>
2010-12-01 14:19     ` [msysGit] " Erik Faye-Lund
2010-12-01 14:41 ` [PATCH v2] Documentation/config.txt: Order variables alphabetically Jari Aalto
2010-12-01 15:25   ` [PATCH v3] " jari.aalto
2010-12-01 16:13     ` Jonathan Nieder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=tm9wX08_o2xgmSS371atgsfPqydT-AZLYxNwJ@mail.gmail.com' \
    --to=kusmabite@gmail.com \
    --cc=engg.bahl@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=msysgit@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).