Skip to content

Commit

Permalink
problem: log-pace flag usage antiquated
Browse files Browse the repository at this point in the history
solution: update it and simplify
  • Loading branch information
whilei committed Jul 28, 2017
1 parent 80f7222 commit 6f530fe
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions cmd/geth/flags.go
Original file line number Diff line number Diff line change
Expand Up @@ -155,9 +155,8 @@ var (
}
LogPaceFlag = cli.StringFlag{
Name: "log-pace",
// TODO: Incompatible is overstated. But there are nuances of their integration that must be considered and negotiated further.
Usage: `Toggle paced logging instead of event-based logging. Values must be of the form N(m|s), where N is a positive integer, and (m|s) is the literal 'm' or 's' designating _m_inute or _s_econd. This option is INCOMPATIBLE with the verbosity and vmodule flags.`,
Value: "1m",
Usage: `Toggle paced logging instead of event-based logging. Argument value should be interval in seconds.`,
Value: "60",
}
BacktraceAtFlag = cli.GenericFlag{
Name: "backtrace",
Expand Down

0 comments on commit 6f530fe

Please sign in to comment.