| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
removed code not actually needed in imupd
|
|\ |
|
| | |
|
| |\ |
|
| | |\ |
|
| | | |\
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
runtime/net.c
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
because getnameinfo() is not cancel-safe, but was not guarded against
being cancelled. pthread_cancel() is routinely being called during
HUP processing.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
thanks to Michael Biebl for suggesting it
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
problem source is that getnameinfo() is not cancel-safe,
not that it is not thread-safe. It is now guarded against
cancellation.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... but removed the mutex, as the problem seems to be in cancel
processing, so the mutex is no longer necessary
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- changed sequence when awakening thread
- removed no longer needed condition variable
- EXPERIMENTALLY added mutex guarding to hostname lookups
this is to be removed if it does not have any verifyable
useful effect
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I am changing the way the version number is bumped so that
viewer git merge conflicts happen. In the future, it will
be bumped immediately before release and not immediately after
(though this means I need to be more careful with interim
versions).
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | |/ /
| | |/| |
| | | | |
| | | | |
| | | | | |
Conflicts:
doc/troubleshoot.html
|
| | |\ \ \
| | | | |/
| | | |/| |
|
| | | | | |
|
|\ \ \ \ \
| | |_|_|/
| |/| | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- removed newly-introduced potential deadlock in debug system
- removed unnecessary pthread_cond_signal
- a bit general cleanup
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
runtime/debug.c
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
multi-threading
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
destructor not yet permitted because verification is
missing that a atomic opration is sufficient for the
job required
|
| |\| | | |
|
| |\ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The code was potentially race, at least on systems where
a memory barrier was needed. Fix not fully tested yet.
|
|\ \ \ \ \ \
| | |_|/ / /
| |/| | | | |
|
| |\ \ \ \ \
| | |_|/ / /
| |/| | / /
| | | |/ /
| | |/| | |
|
| | |\ \ \
| | | | |/
| | | |/| |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... as $...OnlyIfPrev... in some parts of the documentation. Thanks to
Lorenzo M. Catucci for reporting this bug.
|
|\| | | | |
|
| |\| | | |
|
| | |\| |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It did not properly de-init a variable acting as a linked list head.
That resulted in trying to access freed memory blocks after the HUP.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... for the purpose of conducting a few external tests. This is a
first approach at removing the time() call in the output, but it shows
there are some subleties we need to address.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
... I think it may be useful to extend this later, thus I move it
into git.
|
|\ \ \ \ \
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
There was a wrong order of mutex lock operations. It is hard to
believe that really caused problems, but in theory it could and with
threading we often see that theory becomes practice if something is only
used long enough on a fast enough machine with enough CPUs ;)
|
| | | | | |
|
| |/ / / |
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
...for setting controlling worker thread shutdown period
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
... but did not manage to avoid doing at least one call. So
this change introduced performance benefit only in a few
non-common situations. Anyhow, it hopefully levels ground
for better things to come.
|