again,
Alan
-Original Message-
From: [EMAIL PROTECTED] on behalf of Dave Shield
Sent: Tue 12/19/2006 6:46 PM
To: [EMAIL PROTECTED]
Cc: [email protected]
Subject: Re: Difference in Parsing Command-line arguments under Solaris vs.
Linux
On 19/12/06, Alan Cheng <[EM
al Message-
From: Thomas Anders [mailto:[EMAIL PROTECTED]
Sent: Tue 12/19/2006 7:02 PM
To: [EMAIL PROTECTED]
Cc: [email protected]
Subject: Re: Difference in Parsing Command-line arguments under Solaris vs.
Linux
Dave Shield wrote:
> On 19/12/06, Alan Cheng <[EMAIL P
Dave Shield wrote:
> On 19/12/06, Alan Cheng <[EMAIL PROTECTED]> wrote:
>> Why can't we put hostname as the 1st command-line argument under Solaris?
>
> I'd actually ask the opposite question - how come this works under Linux?
Apart from that, the reason is probably the different getopt() impleme
On 19/12/06, Alan Cheng <[EMAIL PROTECTED]> wrote:
> Why can't we put hostname as the 1st command-line argument under Solaris?
I'd actually ask the opposite question - how come this works under Linux?
The documentation specifies that option flags should come *before* the
positional parameters (ho
Hello,
I was hoping someone could help me figuring out why snmpwalk (5.4)
parsing command-line arguments differently under Solaris than Linux.
Under Solaris:
"snmpwalk hostname -c community_string -v 2c OID" would return an error:
No community name specified.
USAGE: snmpwalk [OPTIONS] AGENT [O
