Summary: | python hook in inn ebuild causes innd/nnrpd problems | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Bullinger <consult> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | 1.2 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Thomas Bullinger
2002-06-29 15:29:43 UTC
Using the standard inn ebuild (Latest version Available: 2.3.3) with "python" enabled causes this problem in innd (innd crashes): innd: SERVER cant exec in èHo/news/bin/nnrpd No such file or directory innd: SERVER cant exec in (Ìõ/news/bin/nnrpd No such file or directory ... I build inn without "python" and the problem went away. Also, I changed the "/etc/init.d/innd" script so that it looks like this (use "rc.news" to start the daemon and use "ctlinnd" to throttle/stop it [and take take of innwatch if it runs as well]): #!/sbin/runscript # Copyright 1999-2002 Gentoo Technologies, Inc. # Distributed under the terms of the GNU General Public License, v2 or later # /space/gentoo/cvsroot/gentoo-x86/net-misc/bind/files/named.rc6,v 1.4 2002/06/01 16:31:07 nitro Exp depend() { need net } start() { ebegin "Starting innd" start-stop-daemon --start --quiet --chuid news:news --exec /usr/lib/news/bin/rc.news eend $? } stop() { ebegin "Stopping innd" /usr/lib/news/bin/ctlinnd throttle "Shutdown in preparation" if [ -f /var/spool/news/run/innwatch.pid ] then kill `cat /var/spool/news/run/innwatch.pid` fi start-stop-daemon --stop --quiet --pidfile /var/spool/news/run/innd.pid eend $? } When you say that you built inn with "python" enabled or disabled, how did you go about enabling or disabling python support? The inn ebuild doesn't contain any references to python support, either explicit or implicit. The ebuild file contains the option "--with-python" for the "configure" script, which explicetly enables "python" hooks (in the same way that the line "--with-perl" does that for "perl"). Removing the "--with-python" line did configure and compile "inn" without any "python" hooks, which fixed the problem. It might be a problem with "inn" itself ... but I did not investigate it any further since I had found a workaround :) Daiiii! Look and look and I find nothing. You spent probably *10 seconds* and find it. Thanks. I'll hop back on this one and find out what's going on if I can. I emerged 2.3.3 with python-2.2.1-r5, no problems as far as I can see. Where do you see the error messages below? What compiler/CFLAGS ? |