Proposed argument changes to ntpq (fixing bug #319)

[Ian Bruene]

On 06/08/2017 02:48 PM, Eric S. Raymond via devel wrote:
> Gary E. Miller via devel <devel at ntpsec.org>:
>> Well, more to be learned, my getopt(3p) is not the same as what I see on
>> unix.com.  The online copy did not include the snippet I quoted.  You
>> can confirm on the POSIX site for getopt(3P):
>>
>> http://www.unix.com/man-page/posix/3p/getopt/
>>
>> But they both had this snippet:
>>
>> "A <colon> (':') shall be returned if getopt() detects a missing
>> argument and the first character of optstring was a <colon> (':')."
>>
>> So optional optarg can be valid POXIX.
> I didn't know that.  Thanks.

Unfortunately the documentation / StackOverflow questions / library code 
I've been able to find indicate that this feature does not exist in 
python's getopt.

-- 
In the end; what separates a Man, from a Slave? Money? Power?
No. A Man Chooses, a Slave Obeys. -- Andrew Ryan