Serban,
Two dashes like that indicate "this is the end of option parsing", and
any subsequent data is treated as arguments. In some shells (with some
commands) "-" is interpreted as <STDIN>, so in order to disambiguate,
the "--" are used...
Is tcpclient functioning as you would expect?
-Martin
------------
$ man bash
<snip>
- A single - signals the end of options and dis-
ables further option processing. Any arguments
after the - are treated as filenames and argu-
ments. An argument of -- is equivalent to an
argument of -.
<snip>
On 10 Dec, Serban Udrea wrote:
: On Thu, Dec 09, 1999 at 01:59:13PM -0600, [EMAIL PROTECTED] wrote:
: > Serban,
: >
: > I'd ask the list....but, if you don't get a good response from the list,
: > please feel free to ask me directly, and I'll try to respond promptly...
: >
: > -Martin
: < Here we are at the end of your message >
:
: Hello,
:
: And thanks Martin for answering to my question.
:
: My first problem is about the examples given for the use of tcpclient. Lets
: take who@ (the others are more or less similar):
:
: #!/bin/sh
: # WARNING: This file was auto-generated. Do not edit!
: /usr/local/bin/tcpclient -RHl0 -- "${1-0}" 11 \
: sh -c 'exec /usr/local/bin/delcr <&6' | cat -v
:
: After reading the man page for tcpclient, I think attentively, I couldn't
: figure out at all what are the `--' standing for. So I would be very happy if
: someone could explain me the `--'.
:
: Please note that I'm a beginner in programming and also that I introduced the
: `\' just in this mail to break the long line in the who@ script (although this
: should be harmless also in the script)
:
: Best regards,
:
: Serban
:
--
Martin A. Brown --- SecurePipe Communications --- [EMAIL PROTECTED]
