Bug 14953

Summary: mtrace commands are redundant
Product: Base System Reporter: Karthik Vugane <kvugane>
Component: binAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 2.2.8-STABLE   
Hardware: Any   
OS: Any   

Description Karthik Vugane 1999-11-17 19:30:01 UTC
mtrace command on the cli has redundancy.
When asked to show the output in brief, the "detail" should not appear in the possible completion set.
The brief/detail commands should be exclusive


kvugane@dope> mtrace from-source source 10.6.0.1 group 224.0.1.40 brief ?  
Possible completions:
  <[Enter]>            Execute this command
  detail               Display detailed output
  extra-hops           Extra hops to try past a non-responding router (0..255)
  interval             Interval between statistics gathering (seconds)
  loop                 Loop indefinitely, print rate and loss statistics
  max-hops             Maximum hops to trace toward source (0..255)
  max-queries          Maximum number of query attempts for any hop (1..32)
  multicast-response   Always request the response using multicast
  no-resolve           Don't attempt to print addresses symbolically
  no-router-alert      Don't use the router-alert IP option
  response             Send trace response to host or multicast address
  ttl                  IP time-to-live value (0..255)
  unicast-response     Always request the response using unicast
  wait-time            Time to wait for a response (seconds)
  |                    Pipe through a command
Comment 1 Steve Price freebsd_committer freebsd_triage 1999-12-17 20:46:32 UTC
Responsible Changed
From-To: gnats-admin->freebsd-bugs

Misfiled PR. 
Comment 2 Bill Fenner freebsd_committer freebsd_triage 1999-12-18 01:48:39 UTC
State Changed
From-To: open->closed

This appears to be an internal Juniper PR, sent to FreeBSD by mistake.