X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 	tests=AWL,BAYES_00,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <49EA43CA.8010607@veritech.com>
Date: Sat, 18 Apr 2009 17:19:06 -0400
From: "Lee D.Rothstein" <lee AT veritech DOT com>
Reply-To: Cygwin Tech List <cygwin AT cygwin DOT com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Cygwin Tech List <cygwin AT cygwin DOT com>
Subject: Re: 1.7: Problem with Vista64b ACLs and sockets
References: <49E7764B DOT 7080700 AT veritech DOT com> <20090417094415 DOT GC5200 AT calimero DOT vinschen DOT de> <49E851D1 DOT 4050107 AT cwilson DOT fastmail DOT fm> <20090417100357 DOT GE5200 AT calimero DOT vinschen DOT de> <49E8963F DOT 1040502 AT cwilson DOT fastmail DOT fm> <20090417145639 DOT GA9559 AT calimero DOT vinschen DOT de>
In-Reply-To: <20090417145639.GA9559@calimero.vinschen.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.0.1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

Corinna Vinschen wrote:
> On Apr 17 10:46, Charles Wilson wrote:
>   
>> Corinna Vinschen wrote:
>>
>>     
>>> Yes, sure, but in that case, why not use the native ping?  AFAIK the
>>> ICMP API doesn't provide all the data you need to emulate the usual
>>> UNIX ping output anyway.
>>>       
>> AFAIK, the native (e.g. the shipped-with-windows) ping doesn't use the
>> ICMP dll either. That's why I installed FPing. However, FPing (or even
>> shipped-with-windows ping) are native, not cygwin progs. I don't like
>> using native progs at all, ever, if I can help it. They always lead to
>> surprises: pty issues in terminals, issues with pathnames, difficulties
>> in complex commands (pipes |), etc.
>>
>> But it was just an idle thought.
>>     
>
> No, it's not idle, it's a valid argument.  The problem is, ping isn't
> useful as is for non-Admin users, and the package is orphaned.  That's
> why I think we should drop it from the distro.  If somebody takes over
> maintainance and comes up with a patch which makes ping work for
> non-Admin users again, there's nothing to say against a Cygwin ping.  In
> the current state it just leads to confusion, though.
>
>
> Corinna
>   
First, Corrina, thanks for the info. Because of my other ACL problems I 
was totally confused
as to what was going on. I have, I think fixed these with a combination 
of tools.

Second, my user ID is part of the Administrator group, but you must 
specifically 'run as' Cygwin
to gain true Administrator privilege even from an Administrators group 
ID in order for /bin/ping
to work in my tests. I'm sure you knew this Corinna, but others may not 
have.

Third, I've changed the ping in my profile to use MS ping, and it works 
fine. The parameters are
specified differently, but the exit codes work fine. I tried 'fping', 
but its too noisy about having
to use the ICMP.dll, and the -i option (use the ICMP.dll as a first 
choice rather than raw sockets)
seems not to work.

Now, I understand why 'ping' was missing for so long from Cygwin, and 
why 'traceroute' has
never been a part of it. (Yes, I know about MS 'tracert'.)

Thank you, again, Corinna.





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