Bug#441621: All bacula daemons do not release STDOUT/STDERR on daemonization

2007-09-15 Thread Sven Hartge
Hi. After an update to the recently released 2.2.4 of bacula the problem still persists. Grüße, Sven. -- Sven Hartge -- professioneller Unix-Geek Meine Gedanken im Netz: http://www.svenhartge.de/

Bug#441621: All bacula daemons do not release STDOUT/STDERR on daemonization

2007-09-11 Thread Sven Hartge
Um 17:02 Uhr am 11.09.07 schrieb Sven Hartge: > Right now I am trying to find out, why debug_level is set, even if the > daemons are not started with any debug option. Another indication of debug_level being > 0 is the invocation of print_memory_pool_stats() at the termination of a daemon (line

Bug#441621: All bacula daemons do not release STDOUT/STDERR on daemonization

2007-09-11 Thread Sven Hartge
Um 01:14 Uhr am 11.09.07 schrieb Sven Hartge: > After a quick test and upgrade to a freshly build 2.2.3, I can see this > problem/bug is in all daemons from bacula (director, storage and file). Hmm. The code for daemonization in bacula is found in src/lib/daemon.c in daemon_start(). In line 7

Bug#441621: All bacula daemons do not release STDOUT/STDERR on daemonization

2007-09-10 Thread Sven Hartge
Hi again. After a quick test and upgrade to a freshly build 2.2.3, I can see this problem/bug is in all daemons from bacula (director, storage and file). I don't know what went wrong upstream, but this was not present in 2.0.x. (this lsof output is again from my backport to etch, but the Sid ve