Re: [msysGit] GIT connect "connect to host HOSTNAME port 22: Bad file number" message shown

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



First of all, we don't top-post on these mailing lists, as it makes
the conversation harder to read for other people.

Secondly, don't cull the CC list (hit "reply to all" in GMail) in the
future, so other people is able to read your response.

I've fixed these problems this time, so others might jump in.

On Wed, Dec 1, 2010 at 3:00 PM, GAURAV BAHL <engg.bahl@xxxxxxxxx> wrote:
> On Wed, Dec 1, 2010 at 8:33 AM, Erik Faye-Lund <kusmabite@xxxxxxxxx> wrote:
>>
>> On Wed, Dec 1, 2010 at 1:48 PM, GAURAV BAHL <engg.bahl@xxxxxxxxx> 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.
>
> Thats' what I have done - Security point of view I haven't stated HOSTNAME
> in the inline message
>

OK, then I 'm out of suggestions for now.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]