Superfluous rtlsdr driver & hamlib output circumvents the python logger
Running the latest master with LOG_LEVEL=Warning
, there are superfluous messages spamming the log output:
Mar 14 23:50:32 satnogspi systemd[1]: Started SatNOGS client.
Mar 14 23:56:24 satnogspi satnogs-client[17040]: rot_init called
Mar 14 23:56:24 satnogspi satnogs-client[17040]: dummy: _init called
Mar 14 23:56:24 satnogspi satnogs-client[17040]: rot_register (1)
Mar 14 23:56:24 satnogspi satnogs-client[17040]: rot_register (2)
Mar 14 23:56:24 satnogspi satnogs-client[17040]: dummy_rot_init called
Mar 14 23:56:24 satnogspi satnogs-client[17040]: rot_open called
Mar 14 23:56:24 satnogspi satnogs-client[17040]: dummy_rot_open called
Mar 14 23:56:24 satnogspi satnogs-client[17040]: rot_get_position called
Mar 14 23:56:24 satnogspi satnogs-client[17040]: dummy_rot_get_position called
Mar 14 23:56:24 satnogspi satnogs-client[17040]: rot_set_position called
Mar 14 23:56:27 satnogspi satnogs-client[17040]: Found Rafael Micro R820T tuner
Mar 14 23:56:27 satnogspi satnogs-client[17040]: Found Rafael Micro R820T tuner
Mar 14 23:56:27 satnogspi satnogs-client[17040]: [R82XX] PLL not locked!
Mar 14 23:56:27 satnogspi satnogs-client[17040]: [INFO] Using format CF32.
Mar 14 23:56:29 satnogspi satnogs-client[17040]: Allocating 15 zero-copy buffers
Mar 15 00:06:13 satnogspi satnogs-client[17040]: 4
This output is generated by librtlsdr (librtlsdr.c#L1556) and Hamlib (rot_dummy.c#L91-L96).
While disabling debug output might suppress some messages in case of hamlib, capturing the stdin / stderr output from the subprocesses will enable satnogs-client to decide itself which messages should be written to the logfile or should be ignored.