From 6f530fe0be316e4311157342f4396a8348fc7f11 Mon Sep 17 00:00:00 2001 From: ia Date: Fri, 28 Jul 2017 08:53:13 -0500 Subject: [PATCH] problem: log-pace flag usage antiquated solution: update it and simplify --- cmd/geth/flags.go | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/cmd/geth/flags.go b/cmd/geth/flags.go index e2042a4bf..b9f109d91 100644 --- a/cmd/geth/flags.go +++ b/cmd/geth/flags.go @@ -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",