Bug 43445 - adjust samba4 debug level at runtime
adjust samba4 debug level at runtime
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
https://bugzilla.samba.org/show_bug.c...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-30 13:35 CET by Jens Thorp-Hansen
Modified: 2019-01-03 07:19 CET (History)
4 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Thorp-Hansen univentionstaff 2017-01-30 13:35:10 CET
Most if not all adjustments need restarts etc. of the univention-samba4 service. It would be great if adjustments could be made (i.e. debuglevel) at runtime.
Comment 1 Florian Best univentionstaff 2017-01-30 14:45:12 CET
Can you give more details on which settings you mean?
We could implement a signal handler for reloading the loglevel.
Comment 2 Arvid Requate univentionstaff 2017-01-30 18:01:32 CET
See URL.
Comment 3 Arvid Requate univentionstaff 2017-04-24 17:09:54 CEST
I've looked into this last week:

* The python-bindings for the internal messaging in source4 could be used for this (even though they are incomplete), but apparently the source4-daemons don't register the according messages MSG_REQ_DEBUGLEVEL. In contrast the source3 daemons (smbd/nmbd/winbind) seem to use lib/util/debug_s3.c, which registers this message. So this is the research part, now somebody has to do the development.
Comment 4 Stefan Gohmann univentionstaff 2019-01-03 07:19:08 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.