You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using librespot as systemd service, with the default recommended options (herrernst binary for raspberry)
Very quickly the journal fills up with librespot output such as
librespot::audio_file2: Got channel 30
....
This can be fixed in the systemd service definition by adding
/dev/null 2>&1 &
However this mutes all output; and since librespot is mature, wouldn't it make sense for it to by less chatty by default - just output the key messages important to the log such as
started
authenticated
started playing
stopped playing
and activate all the current "debug" info (chunk downloads, volume changes etc) only when passed a --verbose command line option
The text was updated successfully, but these errors were encountered:
You can reduce log level by setting RUST_LOG environment variable to the desired level: https://doc.rust-lang.org/log/env_logger/
I recommend adding this line in the [Service] section of the systemd unit: Environment="RUST_LOG=info"
Agreed, that was too verbose. Thanks for opening the issue.
I've changed the default level to info, with a --verbose argument to switch to trace.
The RUST_LOG environment variable still can still be used as well.
mjaggard
pushed a commit
to mjaggard/librespot
that referenced
this issue
Mar 21, 2018
Using librespot as systemd service, with the default recommended options (herrernst binary for raspberry)
Very quickly the journal fills up with librespot output such as
librespot::audio_file2: Got channel 30
....
This can be fixed in the systemd service definition by adding
However this mutes all output; and since librespot is mature, wouldn't it make sense for it to by less chatty by default - just output the key messages important to the log such as
started
authenticated
started playing
stopped playing
and activate all the current "debug" info (chunk downloads, volume changes etc) only when passed a --verbose command line option
The text was updated successfully, but these errors were encountered: