From b1099a5b560db0145534ed6484eee27c7d93528a Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Mon, 1 Nov 2010 20:55:04 +1100 Subject: s3-libsmbclient Add comments to describe the behaviour of DEBUG() This isn't quite what you would expect from this interface, but actually avoids some really nasty situations if you ever have more than one libsmbclient context in a process. In the real world, if you have asked for DEBUG() to stderr in one part of the code, you will want it globally, even in a different thread (which in the past would have rest everything to stdout again, at least while starting up). Andrew Bartlett --- source3/lib/debug.c | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'source3/lib') diff --git a/source3/lib/debug.c b/source3/lib/debug.c index f9f4cae000..a97c0bf923 100644 --- a/source3/lib/debug.c +++ b/source3/lib/debug.c @@ -614,6 +614,11 @@ static void debug_close_fd(int fd) } } +bool debug_get_output_is_stderr(void) +{ + return (state.logtype == DEBUG_DEFAULT_STDERR) || (state.logtype == DEBUG_STDERR); +} + /************************************************************************** reopen the log files note that we now do this unconditionally -- cgit