9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Maurício CA" <mauricio.antunes@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Different results for the same rc script when using listen1
Date: Sun, 24 Apr 2011 17:05:43 +0000	[thread overview]
Message-ID: <ip1l97$naq$1@dough.gmane.org> (raw)
In-Reply-To: <86wrijennb.fsf@cmarib.ramside>

>> How can running a script throw 'listen1' can get 'rc' to fail an
>> 'if' test?!?!

> This looks like you're using p9p.  Have you checked your PATH?
> It might not be finding an executable, or finding the wrong version
> of an executable.

Sure. Take, for instance, this script uniquely named 'tester.rc':

   #!/usr/bin/env rc
   echo -n I am the real tester:
   ~ $1 $2

I can change 'listen_test.rc' to use it:

   #!/usr/bin/env rc
   for (i in `{seq 1 5}){
       if (./tester.rc $i 3) {
           echo ' ' $i equals 3
       }
       if not echo ' ' $i is different from 3
   }

Now I get:

   $./listen_test.rc
   I am the real tester:  1 is different from 3
   I am the real tester:  2 is different from 3
   I am the real tester:  3 equals 3
   I am the real tester:  4 is different from 3
   I am the real tester:  5 is different from 3

But:

   $listen1 'tcp!localhost!8080' ./listen_test.rc &
   $dial -e 'tcp!localhost!8080'
   I am the real tester:  1 equals 3
   I am the real tester:  2 equals 3
   I am the real tester:  3 equals 3
   I am the real tester:  4 equals 3
   I am the real tester:  5 equals 3


Thanks,

Maurício





  reply	other threads:[~2011-04-24 17:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-24  5:09 Maurício CA
2011-04-24  5:22 ` andrey mirtchovski
2011-04-24  7:30   ` Maurício CA
2011-04-24 14:20 ` smiley
2011-04-24 17:05   ` Maurício CA [this message]
2011-04-24 17:17     ` Bakul Shah
2011-04-25  0:16       ` Maurício CA
2011-04-25  2:00         ` Anthony Martin
2011-04-25  3:14           ` Maurício CA
2011-04-25  3:17           ` erik quanstrom
2011-04-25  3:36             ` erik quanstrom
2011-04-25  3:58               ` Bakul Shah
2011-04-25  4:39                 ` erik quanstrom
2011-04-25  5:27                   ` Lyndon Nerenberg
2011-04-25  5:53                   ` Bakul Shah
2011-04-25  6:59                     ` Robert Ransom
2011-04-25 14:56                       ` Bakul Shah
2011-04-25 15:00                         ` erik quanstrom
2011-04-25 16:17                         ` Skip Tavakkolian
2011-04-25 16:27                           ` Joseph Stewart
2011-04-25 20:13                           ` smiley
2011-04-25 20:16                             ` Lyndon Nerenberg
2011-04-25 20:18                             ` erik quanstrom
2011-04-25 14:44                     ` erik quanstrom
2011-04-25 13:53               ` Maurício CA
2011-04-25 14:42                 ` erik quanstrom
2011-04-27 21:57                   ` Maurício CA
2011-04-26  9:02               ` dexen deVries
2011-04-26 12:57                 ` erik quanstrom
2011-04-25  2:03         ` andrey mirtchovski
2011-04-25  2:14           ` Iruatã Souza
2011-04-25  2:20             ` andrey mirtchovski

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='ip1l97$naq$1@dough.gmane.org' \
    --to=mauricio.antunes@gmail.com \
    --cc=9fans@9fans.net \
    /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).