cmdline_s4: re-initialise logging once loadparm is ready
authorDouglas Bagnall <douglas.bagnall@catalyst.net.nz>
Thu, 26 May 2022 03:46:08 +0000 (15:46 +1200)
committerAndreas Schneider <asn@cryptomilk.org>
Mon, 30 May 2022 10:11:28 +0000 (10:11 +0000)
commit9537ac723cfdc43e718fdd08dc28883e7057a372
treeec5d11c7277788bad162ea965590d63aeec02f24
parent5e00c230ec8d37044205a16c3a6ceaa64de382d0
cmdline_s4: re-initialise logging once loadparm is ready

The first time round we maybe didn't know which files we wanted to log to.
Suppose, for example, we had an smb.conf with

 log level = 1 dsdb_group_json_audit:5@/var/log/group_json.log

we wouldn't see anything in "/var/log/group_json.log", while the level
5 dsdb_group_json_audit messages would go into the main log.

Note that the named file would still be opened by winbindd and others
that use the s3 code, but would remain empty as they don't have anything
to say about dsdb_group_json_audit.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=15076

Signed-off-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Andreas Schneider <asn@samba.org>
lib/cmdline/cmdline_s4.c