ip: update man pages and usage() for 'ip monitor'
Sync with the current code. Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
This commit is contained in:
parent
743a00a72b
commit
cbe195dc6b
|
|
@ -29,7 +29,10 @@ int prefix_banner;
|
|||
|
||||
static void usage(void)
|
||||
{
|
||||
fprintf(stderr, "Usage: ip monitor [ all | LISTofOBJECTS ]\n");
|
||||
fprintf(stderr, "Usage: ip monitor [ all | LISTofOBJECTS ] [ FILE ]\n");
|
||||
fprintf(stderr, "LISTofOBJECTS := link | address | route | mroute | prefix |\n");
|
||||
fprintf(stderr, " neigh | netconf\n");
|
||||
fprintf(stderr, "FILE := file FILENAME\n");
|
||||
exit(-1);
|
||||
}
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
.TH IP\-MONITOR 8 "20 Dec 2011" "iproute2" "Linux"
|
||||
.TH IP\-MONITOR 8 "13 Dec 2012" "iproute2" "Linux"
|
||||
.SH "NAME"
|
||||
ip-monitor, rtmon \- state monitoring
|
||||
.SH "SYNOPSIS"
|
||||
|
|
@ -6,8 +6,8 @@ ip-monitor, rtmon \- state monitoring
|
|||
.ad l
|
||||
.in +8
|
||||
.ti -8
|
||||
.BR "ip monitor" " [ " all " |"
|
||||
.IR LISTofOBJECTS " ]"
|
||||
.BR "ip " " [ ip-OPTIONS ] " "monitor" " [ " all " |"
|
||||
.IR LISTofOBJECTS " ] [ file " FILENAME " ]
|
||||
.sp
|
||||
|
||||
.SH DESCRIPTION
|
||||
|
|
@ -20,12 +20,13 @@ Namely, the
|
|||
command is the first in the command line and then the object list follows:
|
||||
|
||||
.BR "ip monitor" " [ " all " |"
|
||||
.IR LISTofOBJECTS " ]"
|
||||
.IR LISTofOBJECTS " ] [ file " FILENAME " ]
|
||||
|
||||
.I OBJECT-LIST
|
||||
is the list of object types that we want to monitor.
|
||||
It may contain
|
||||
.BR link ", " address " and " route "."
|
||||
.BR link ", " address ", " route ", " mroute ", " prefix ", "
|
||||
.BR neigh " and " netconf "."
|
||||
If no
|
||||
.B file
|
||||
argument is given,
|
||||
|
|
@ -34,7 +35,9 @@ opens RTNETLINK, listens on it and dumps state changes in the format
|
|||
described in previous sections.
|
||||
|
||||
.P
|
||||
If a file name is given, it does not listen on RTNETLINK,
|
||||
If a
|
||||
.I FILENAME
|
||||
is given, it does not listen on RTNETLINK,
|
||||
but opens the file containing RTNETLINK messages saved in binary format
|
||||
and dumps them. Such a history file can be generated with the
|
||||
.B rtmon
|
||||
|
|
|
|||
Loading…
Reference in New Issue