| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Call setsid() once only to make sure we get a process that is not a
session leader or process group leader, and hence cannot acquire a
controlling terminal.
It looks like setpgid() (or setpgrp()) is used only when setsid() is not
available.
It looks like the call to ioctl() is necessary only for 4.3BSD.
(Patch modified by Lennart Poettering)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
daemon_close_allv()
No Avahi daemon is running. If I start it at command-line
with
etc/init.d/avahi-daemon start
or simply with
avahi-daemon -D
then the avahi-daemon eats all CPU-time.
Stracing the process shows, that it loops endlessly in
gettimeofday({1231956423, 692711}, NULL) = 0
gettimeofday({1231956423, 692735}, NULL) = 0
poll([{fd=5, events=POLLIN}, {fd=15, events=POLLIN}, \
{fd=14, events=POLLIN}, {fd=13, events=POLLIN}, \
{fd=12, events=POLLIN}, {fd=11, events=POLLIN}, \
{fd=10, events=POLLIN}, {fd=8, events=POLLIN}], 8, 62150) = 1 \
([{fd=5, revents=POLLNVAL}])
The fd=5 is a BADFD.
I found out that the fd was closed by daemon_retval_send() from libdaemon.
(But: I think avahi-daemon should handle the POLLERR nevertheless.)
Looking in libdaemon I found, that the library had already closed the fd=5
in daemon_close_all(), and closed it "again" as _daemon_retval_pipe[0] in
daemon_retval_send() -> daemon_retval_done(), but in the meantime, this
is an fd from the application, not from the library. I think, after closing
_daemon_retval_pipe[0] in daemon_close_allv() the fd must be marked as closed.
I have attached a patch. For me it works fine.
|
| |
|
|
|
|
|
| |
see https://bugzilla.novell.com/show_bug.cgi?id=449728
The patch I packaged up for this is attached.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
references.
This is important to make sure that no bugs are introduced that breaks
when using --as-needed.
|
| |
| |
| |
| |
| | |
Also use the new CC_CHECK_CFLAGS_APPEND macro instead of doing the for
loop manually.
|
| | |
|
| |
| |
| |
| | |
Issue pointed out by Charles Lindsay.
|
|/ |
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
This will allow to explicitly check for support of the new extensions
(like verbosity).
|
| | |
|
| |
| |
| |
| |
| | |
Reduces warnings about unused variables by not declaring them if they
are under an #ifdef conditional.
|
| |
| |
| |
| |
| |
| |
| | |
On OpenSolaris, the _NSIG macro is not defined, but NSIG is; as it's
not possible to use NSIG under glibc (it would miss the SIGRT*
series), define a SIGNAL_UPPER_BOUND depending on the system (and
error out if the system lacks both NSIG and _NSIG).
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| | |
Reduces warnings about unused variables by not declaring them if they
are under an #ifdef conditional.
|
| |
| |
| |
| |
| |
| |
| | |
On OpenSolaris, the _NSIG macro is not defined, but NSIG is; as it's
not possible to use NSIG under glibc (it would miss the SIGRT*
series), define a SIGNAL_UPPER_BOUND depending on the system (and
error out if the system lacks both NSIG and _NSIG).
|
|/
|
|
|
| |
With this variant, it's possible to build against a live tree of
libdaemon to test in-development features.
|
|
|
|
|
| |
As many 0pointer projects use the same code, move it out on its own
macro, and use that. The macro can then be shared across projects.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of writing custom code to check for cflags checking, import a
copy of attributes.m4 from xine-lib's repository and use the
CC_CHECK_CFLAGS macro.
The advantage lies not only in being able to reduce the custom code in
configure.ac, but also in the fact that the CC_CHECK_CFLAGS macro
caches the results, making ./configure -C quite faster on second run.
Check for the CFLAGS for any compiler and not just GCC, if the
compiler does support the flag it is better to u se it anyway,
otherwise it will be skipped.
|
|
|
|
|
|
|
| |
Older versions of libtool (pre-2.2) made this change unimportant as
C++ and Fortran compilers were always checked for. Newer libtool
versions solve this problem, so it makes configure faster not to check
for it.
|
|
|
|
|
|
|
|
|
| |
Instead of just checking if the compiler supports -std=gnu99 option,
make use of the autoconf macro for discovering C99. This way other
non-GCC compiler could be used in C99 mode too.
If the compiler does not support gnu99 it falls back to c99, giving
more chances that it would work than leaving it to default.
|
|
|
|
|
| |
Make it known to autoconf and aclocal, add ignore file for libtool 2.2
macro files.
|
|
|
|
|
|
|
| |
In recent versions of autoconf, the AC_HEADER_ASSERT check not only
makes sure that the assert.h header is found but it also allows the
user to decide whether to enable or disable assertions at ./configure
(rather than having to pass -DNDEBUG manually).
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Install and distribute README.html and style.css in the html
directory.
Install and distribute README in the doc directory.
The htmldir and docdir entries are added by recent versionf of
autoconf and are configurable, so that distributions don't need to
handle installation of these manually.
|
|
|
|
|
| |
Replaces AC_GNU_SOURCE with AC_USE_SYSTEM_EXTENSIONS and
AC_HELP_STRING with AS_HELP_STRING (and quotes its parameters).
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
anyway
This reverts commit b05a9ea7518befdae73772becaf9bc4b11711f80.
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|