Get desktop application:
View/edit binary Protocol Buffers messages
Attempt to set a command line flag. Note that many command line flags do not take effect if changed at runtime. TODO: We plan to add tags indicating which flags can be modified at runtime. For now, this is an advanced option.
Force the change, even if the flag is not marked as safe to change at runtime. This can cause crashes or other bad behavior, so should only be used as a last resort.
A string describing the new value that the option has been set to. This passes through the return value of SetCommandLineOption() from gflags, which doesn't specify anything about the format of this message. Using 'result' above is more reliable.
If the flag exists, the prior value of the flag. This is set even in the case of BAD_VALUE.
Get the value of the gflag with the given flag name.
If the flag name is valid, the value is set to its current value. Else the valid field will be set to false.
RPC will fail on errors.
(message has no fields)
(message has no fields)
(message has no fields)
(message has no fields)
Attempt to flush coverage information to disk, if running a coverage build.
(message has no fields)
If the current build is not a coverage build, returns false.
Requests the server's current hybrid_time.
(message has no fields)
The current hybrid_time of the server.
Requests the server's status and version info
(message has no fields)
(message has no fields)
(message has no fields)
(message has no fields)
(message has no fields)
The status information dumped by a server after it starts. This is optionally exposed on the local host in a text file which the server writes out at startup. Additionally, it is exposed via RPC through the GenericService interface.
Used in:
Used in:
The flag is not safe to change at runtime without the 'force' flag.