mirror of
git://git.code.sf.net/p/dhcpd-pools/code
synced 2025-12-16 15:57:00 +00:00
remove upper limit of sort order definitions
Unlikely to be needed by anyone, but because arbitrary limits are from code style point of view ugly. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
This commit is contained in:
parent
327691f34a
commit
0369340710
5 changed files with 72 additions and 59 deletions
|
|
@ -57,9 +57,9 @@ or monitor subset of data.
|
|||
Path to the dhcpd.leases file.
|
||||
.TP
|
||||
\fB\-s\fR, \fB\-\-sort\fR=\fI[nimcptTe]\fR
|
||||
Sort ranges by chosen fields as a sorting keys. Maximum of five sort keys
|
||||
can be defined. Keys weight from left to right, i.e., if more weighting keys
|
||||
are equal next one is used. The IP field is default sort key.
|
||||
Sort ranges by chosen fields as a sorting keys. Keys weight from left to
|
||||
right, i.e., if more weighting keys are equal next one is used. The IP
|
||||
field is default sort key.
|
||||
.TP
|
||||
\fB\-r\fR, \fB\-\-reverse\fR
|
||||
Sort results in reverse order.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue