--- Jonas Meurer <[EMAIL PROTECTED]> wrote:
> On 05/02/2007 Max Hyre wrote:
> >Dear Debianists:
> >
> >Between two successive calls to ping, it
> crapped out.
> > (Tried twice in a row because I had a flaky DSL
> connection,
> > and wanted to see whether it had decided to join
> the party
Jonas Meurer wrote:
> I guess that the problem is '-n 1'. According to the ping manpage, the
> option '-n' takes no argument:
AAARRRrrrghh! I should have used `-c 1'. I'm so used to using another
implementation that uses -n for the number of pings that I forgot to
check what I was doing. That
On 05/02/2007 Max Hyre wrote:
>Dear Debianists:
>
>Between two successive calls to ping, it crapped out.
> (Tried twice in a row because I had a flaky DSL connection,
> and wanted to see whether it had decided to join the party.)
>
> ==
> [EMAIL PROTECTED]:~# i
{sa_family=AF_INET, sin_port=htons(1025),
sin_addr=inet_addr("0.0.0.1")}, 16) = -1 EINVAL (Invalid argument)
======
o Asking Google about `"0.0.0.1" "ping: invalid argument"'
returns precisely zip.
o It returns some stuff from a search
4 matches
Mail list logo
