Misleading benign log messages

[bjourne]

[  109.017291 <    0.058744 >] polkitd[928]: Started polkitd version 126
[  109.019911 <    0.002620 >] polkitd[928]: Loading rules from directory /etc/polkit-1/rules.d
[  109.020163 <    0.000252 >] polkitd[928]: Loading rules from directory /run/polkit-1/rules.d
[  109.020182 <    0.000019 >] polkitd[928]: Error opening rules directory: Error opening directory “/run/polkit-1/rules.d”: No such file or>
[  109.020184 <    0.000002 >] polkitd[928]: Loading rules from directory /usr/local/share/polkit-1/rules.d
[  109.020189 <    0.000005 >] polkitd[928]: Error opening rules directory: Error opening directory “/usr/local/share/polkit-1/rules.d”: No >
[  109.020193 <    0.000004 >] polkitd[928]: Loading rules from directory /usr/share/polkit-1/rules.d
[  109.021553 <    0.001360 >] polkitd[928]: Finished loading, compiling and executing 2 rules

While these messages are logged at priority level 5, they include the word "error" indicating that something is wrong. But this is normal operation so the messages should be rephrased. Also consider removing them since they are not useful for debugging.

[bluca]

Fixed by #605

[jrybar-rh]

Fixed by #605

I think the reporter meant to highlight that while the message is labeled LOG_LEVEL_INFO : LOG_LEVEL_WARNING, the wording still contains the word "error". I think a simple reword can be made in the future release. That's a fastfix.

[jrybar-rh]

consider removing them since they are not useful for debugging

Oh yes, they are :)
The message reflects an error opening any of the configuration directories. Separating the message just for these two that are usually unused, would introduce more code and possible discrepancy AND debugging issues.

I can imagine a scenario where the permissions of the directories are mistakingly customized, so that the daemon cannot open them and voilá, we can see the error message in the journal. That's just the first thing that came to me.

[bjourne]

consider removing them since they are not useful for debugging

Oh yes, they are :) The message reflects an error opening any of the configuration directories. Separating the message just for these two that are usually unused, would introduce more code and possible discrepancy AND debugging issues.

Then consider logging summaries: "Loaded rules from , , ... Could not open directories , , ..." Excessive logging is a nuisance.