Bug 11389 - Change connection logging back to log level 1
Summary: Change connection logging back to log level 1
Status: RESOLVED WONTFIX
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.1.6
Hardware: All All
: P5 trivial (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-07 21:15 UTC by Josh Kelley
Modified: 2023-06-06 22:27 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Kelley 2015-07-07 21:15:02 UTC
Could the non-IPC log level for "connected to service" and "connection closed" be changed back to 1?

Or is there another, comparably easy way of logging service connections and disconnections, without the clutter of raising the log level for a large part of the Samba system?

I saw commits aad5eeb9b4 and 321404ac25, which changed the log level to clean up "make test"'s output, but from an end user's perspective, I think they should be included. I've always interpreted the default log level 1 as "stuff a sysadmin might want to know in everyday operation," and I've always thought that connections to shares and disconnections from shares fall under this category. It's useful for tracking and auditing purposes, and it's a decent parallel to other services' events, like SSH logons and logoffs, that are also logged by default.
Comment 1 Björn Jacke 2023-06-06 22:27:21 UTC
sorry, no, level 1 has been WARNING level. A share connection does not justify a warning level message.