Snapd does not honor log level settings from config or command line flags for startup log messages.

[lynxbat]

❯ go run ./snapd.go -t 0 -l 1                                                                                                                                                                                                                                                                     
INFO[0000] Starting snapd (version: unknown)            
INFO[0000] setting GOMAXPROCS to: 1 core(s)             
INFO[0000] Setting work manager queue size               _block=New _module=scheduler value=25
INFO[0000] Setting work manager pool size                _block=New _module=scheduler value=4
INFO[0000] Configuring REST API with HTTPS set to: false  _module=_mgmt-rest
INFO[0000] REST API is enabled                          
INFO[0000] control started                               _block=start _module=control
INFO[0000] module started                                _module=snapd block=main snap-module=control
INFO[0000] scheduler started                             _block=start-scheduler _module=scheduler
INFO[0000] module started                                _module=snapd block=main snap-module=scheduler
INFO[0000] Starting REST API on :8181                    _module=_mgmt-rest
INFO[0000] REST started                                  _block=start _module=_mgmt-rest
INFO[0000] module started                                _module=snapd block=main snap-module=REST
INFO[0000] setting plugin trust level to: disabled      
INFO[0000] auto discover path is disabled               
INFO[0000] snapd started 

It looks like the log level filtering is not set till after other operations are handled first.

[geauxvirtual]

This was part of the design to always have configuration information for snapd present in the stdout or in the log files no matter the log level set by the user for troubleshooting purposes.

[lynxbat]

That doesn't make sense. If the user sets the log level to WARN they explicitly saying that don't want to see INFO or DEBUG. We should honor that.

[geauxvirtual]

And we do after we print configuration data out, so that when they have an
issue and we ask for log data, we get the picture from when they were
running snapd when it failed. Not when they re-ran snapd with a different
log level setting just so we can configuration information.

But you know best.

On Fri, Apr 29, 2016 at 12:18 PM, Nicholas Weaver notifications@github.com
wrote:

That doesn't make sense. If the user sets the log level to WARN they
explicitly saying that don't want to see INFO or DEBUG. We should honor
that.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#889 (comment)

Justin Guidroz

[lynxbat]

Which is solved by running -l 1

It is no different than running go test and go test -v