LFCS · Question #312
The log level parameter in smb.conf should normally not be set higher than 2 because:
The correct answer is D. The server flushes the log file after each operation, which affects overall performance. Setting the Samba log level parameter higher than 2 is generally discouraged because it causes frequent log file flushes, leading to significant performance degradation.
Question
Options
- ACredentials supplied by the user are logged, which poses a security risk.
- BThe increased verbosity has a negative impact on network bandwidth.
- CMost Samba administrators cannot understand the information presented at higher log levels.
- DThe server flushes the log file after each operation, which affects overall performance.
How the community answered
(21 responses)- C5% (1)
- D95% (20)
Why each option
Setting the Samba log level parameter higher than 2 is generally discouraged because it causes frequent log file flushes, leading to significant performance degradation.
While very high log levels can expose sensitive information, the primary and most immediate reason to avoid them is the severe performance impact, not solely the logging of credentials.
The increased verbosity primarily impacts local disk I/O and CPU usage for processing log data, rather than directly affecting network bandwidth.
The administrator's understanding of log information is irrelevant to the technical performance implications of verbose logging.
When the `log level` in `smb.conf` is set above 2, Samba generates an excessive amount of log data, often flushing this information to disk after nearly every operation. This high frequency of disk I/O operations consumes significant system resources and severely impacts the overall performance of the Samba server.
Concept tested: Samba logging performance impact
Source: https://www.samba.org/samba/docs/current/manpages/smb.conf.5.html
Topics
Community Discussion
No community discussion yet for this question.