Arch Linux

GeneArch

Member

Registered: 2013-07-28

Posts: 110

Re: The IWD thread

sorry - that was clearly bad idea!

What about changing log level down -  edit the systemd service with something like

ExecStart=
ExecStart=/usr/lib/iwd/iwd -l warn

one_half_3544

Member

Registered: 2021-04-23

Posts: 10

Re: The IWD thread

'warn' would not have worked as the 'info' is higher than that (priorities are defined here https://kernel.googlesource.com/pub/scm … /log.h#18), but even going down to 'error' does not help ;(

# ps ax | grep iwd
   5994 ?        Ss     0:01 /usr/libexec/iwd -l error

(https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/doc/coding-style.txt#n320 has the full list of log levels)

UPD:
ok, the https://git.kernel.org/pub/scm/network/ … HACKING#n8 mentions that the patches should be sent to iwd@lists.linux.dev

Last edited by one_half_3544 (Today 14:18:15)

GeneArch

Member

Registered: 2013-07-28

Posts: 110

Re: The IWD thread

Ok - so are you planning to send a patch? What's your thinking, limit the AP probe logging to appropriate level ?

one_half_3544

Member

Registered: 2021-04-23

Posts: 10

Re: The IWD thread

Ok - so are you planning to send a patch? What's your thinking, limit the AP probe logging to appropriate level ?

Yes, I'll send a patch - at least to start a discussion: perhaps people there would come up with a different solution.

Although, yes, to me those are rather 'debug' level prints, and that could be fixed.