We need a tool to change the debug level of samba at runtime, i.e. without the requirement to restart samba, in the same way as smbcontrol can be used to change the debuglevel of smbd, nmbd, and winbindd.
Since samba forks smbd it is not acceptable to restart samba including the file server component to change the debug level.
In the long run we plan to reconsile the messaging systems of the source3 and source4 parts of samba, and then we will have a single tool to control all components. But for 4.0 we should just spend the minimum required effort, which would probably be to integrate it into smbcontrol.
I think we can't release 4.0 into production without having a means to change the debug level at run time.
I agree that it's very important for debugging to be able to change the debug level at run time, but I don't think that this should be a blocker for 4.0 now.
No user raised this issue up to rc5 and I would like to avoid adding new binaries at this late stage in the release process. Would it be an option to make this one a blocker for 4.1?
Agreed. Let's not block 4.0 for this, but let's try to do something like this soon...
I just stumbled across this ... Not sure this is still relevant.
The common message bus means we can talk from smbcontrol to 'samba', we just need to hook up the other end, just as has been done for talloc dumps etc.