The man page for papd in netatalk-2.0.2-1 claims that when papd is run with -d, it prints information to stderr. It lies. When I run papd with -d, it fails silently (it apparently thinks there's something wrong with my papcap file, a separate issue which I'm still debugging). This snippet of output from strace run on "papd -d -f /etc/atalk/papd.conf" is revealing: 5981 open("/", O_RDONLY|O_LARGEFILE) = 3 5981 dup2(3, 1) = 1 5981 dup2(3, 2) = 2 I think perhaps papd is calling daemon() even when it is run with "-d". I don't think it should be doing that.
This bug should now be fixed with netatalk-2.0.3-1, in rawhide-20050617 and available for download from: http://people.redhat.com/~jvdias/netatalk If no problems are found with it, it will shortly be in fc4-updates. There is also an FC-3 version for i386 in the FC3 directory. Please try out this version and let me know of any issues. Thank You!
I have netatalk-2.0.3-2, compiled on July 20, 2005, and this problem persists, even down to the open("/") and dup2() calls still showing up in the strace output. I'm not sure why you thought this was fixed in 2.0.3-1, but it doesn't seem to be.
Sorry for the misunderstanding. You said: "I think perhaps papd is calling daemon() even when it is run with '-d'. I don't think it should be doing that. " I tested 'papd -d' with netatalk-2.0.3 - it does NOT daemonize (fork into the background), and does emit debug messages to the system log /var/log/messages. Yes, man papd(8) does lie when it says it writes messages to stderr - I'll update the man-page in the next version. You need to send the '*.debug' syslog messsages to some log file in /etc/syslog.conf in order to see them.
[Mass switching of bugs filed against FC4T3 to fc4test3 from test3]
This report targets the FC3 or FC4 products, which have now been EOL'd. Could you please check that it still applies to a current Fedora release, and either update the target product or close it ? Thanks.
Fedora Core 3 and Fedora Core 4 are no longer supported. If you could retest this issue on a current release or on the latest development / test version, we would appreciate that. Otherwise, this bug will be marked as CANTFIX one month from now. Thanks for your help and for your patience.
The man page for papd still says stderr. And I just ran "papd -d" and it logged only one message to stderr: Jul 18 10:07:19 jik2 papd[11464]: restart (2.0.3) before exiting. So I still don't believe this is fixed.
Created attachment 297031 [details] Write debugging output also to stderr when papd is invoked with -d option This patch should fix the problem.
Fixed in netatalk-2.0.3-19.fc9