Age | Commit message (Collapse) | Author |
|
Muks: please verify - thes are current the fixed bugs
with milestone 1.8.0 (i.e. the renamed 1.7.2).
I hope this is correct!
I also hope this was the intended scheme - have bug
lists per version section. Please feel free to edit...
Michael
|
|
Michael
|
|
Signed-off-by: Michael Adam <obnox@samba.org>
|
|
Michael
|
|
Michael
|
|
* mention config reload and upon HUP
* log-reopen (not trunc!) upon HUP
* file-logging as default
Michael
|
|
|
|
Michael
|
|
Now that there is always a log file set, we just check for
syslog being set to TRUE and in that case use syslog logging,
file logging otherwiese.
Michael
|
|
Michael
|
|
Now that there is a default value for LogFile, the case
that neither the log file name nor syslog is configured
can not happen any more.
Michael
|
|
Michael
|
|
So that it can be used for default values of some paths later on.
Michael
|
|
We publish bzip2 compressed tarballs starting with the 1.8.x releases.
|
|
Now that we exit early when !logging_initialized, this
can actually not happen anymore anyways: When logging is
initialized, it was also properly configured.
Michael
|
|
This does for instance happen at startup when logging has not yet been set up.
Michael
|
|
|
|
|
|
|
|
|
|
https://www.banu.com/bugzilla/show_bug.cgi?id=55
This is achieved by streamlining handle_connection, adding
a common cleanup-and-exit poing ("done") and a common
failure exit point ("fail") that reads any pending data
from the client fd first before trying to send back
data (error page or stats page).
The new function get_request_entity that is used here,
does not honour any content-length header. It just calls
select on the client-fd and gets any data that is there
to read.
Michael
|
|
Michael
|
|
Michael
|
|
Michael
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Disabling the regex check seems to be required during cross-compiles,
where it's not possible to test the target's regex library at
compile time.
|
|
|
|
The configure would fail when cross compiling due to the regex check
automatically failing for cross compilation. Since you can't run the
regex binary check, assuming the regex library on the target platform is
working would be the only way to get the build working, or adding a
force for people to control based on their build environment.
Signed-off-by: Michael Adam <obnox@samba.org>
|
|
Michael
|
|
Michael
|
|
Michael
|
|
Michael
|
|
Michael
|
|
This way the logging from the various child processes does not
get clobbered up. Formerly, the different write portions
(time stamp, message, newline) would get mixed from the
various child processes' log messages.
Michael
|
|
Michael
|
|
reload_config().
This can actually fail, and we probably need some way to handle this.
Like an emergency error exit or so...
Michael
|
|
Logging is re-initialized by reload_config() now.
And truncation is wrong anyways: A syslog mechanism will
move the current log file and the reopen-action will just
create a new empty log file upon SIGHUP.
Michael
|
|
This includes reopening the log file (in append mode).
Also switching from syslog to logfile and visa versa are included
when called from the SIGHUP handler.
Michael
|
|
Michael
|
|
When this code is hit, availability of syslog has already
been checked (when reading the config file). So config.syslog == TRUE
only when HAVE_SYSLOG_H is defined.
So I remove the preprocessor checks which only clobber the logic
and make the code harder to read (IMHO).
Michael
|
|
This seemed out of place. Now the information is
stored in the correct places (as log.c:logging_initialized).
This way, we will be able to cleanly re-initialize
logging during config reload (SIGHUP) in subsequent
commits.
Michael
|
|
This is where it actually belongs.
Michael
|
|
This controls whether log_messages should write to the
log file / syslog or rather to the log_message_storage.
This will make the global processed_config_file variable
from main unneccessary in the next step.
Michael
|
|
Michael
|
|
Michael
|