Currently the 'log file' directive is global, hence only 1 log file can be created.
In addition to this, having a each module log to seperate log file would be beneficial when large amounts of modules are used. We have >200 module entries and have to script to get at the information.
I guess 'transfer logging' would then be ignored if 'log file' directive is present in the module section. If 'log file' is not present in the per module, it then logs to the global log or syslog.
In the trace, this was mounted over loopback
Kernel is Linux version 2.6.17-rc5-default
Samba is Version 3.0.22-9-SUSE-SLES10
Although I could repeat it with current Samba 3 rc later tonight (it fails the same way).
ignore the previous comment - it was for another defect
I've worked up a patch that makes both "log file" and "syslog facility" per-module settings instead of globals. I didn't see any need to affect "transfer logging", as this was already a per-module setting, and the user can set it to "yes" or "no" either globally or locally, as desired.
Created attachment 1954 [details]
The log-file settings can be set differently for each module
This is now in the CVS version.