CUPS, if added to the default run level, starts before eth0 is brought up. Therefor, if I have Listen 192.168.2.21:631 (192.168.2.21 being the local I address) in my /etc/cups/cupsd.conf file, cups fails when starting up. Reproducible: Always Steps to Reproduce: 1. Add a Listen line with an IPaddress:port to your /etc/cupsd.conf file 2. Add cups to default runlevel 3. Reboot your system Actual Results: In the startup messages, immediatly following the Starting cupsd line you should see an exist message. with a status of 99. If you set log level to debug and reboot, the /var/log/cups/error_log will show the error. Expected Results: Cups should start AFTER the network devices so that it can (if desired) bind to a specific local IP address. A workaround that works fine for me but may not for other is to put Port 631 in my /etc/cups/cupsd.conf file instead. Since I only have a single IP address on this machine, it works just fine but it may not for others.
emerge info?
It has nothing to do with the emerge. This would happen on any Linux machine regardless of distro if you tried to load CUPS befoer your network was up and there was a Listen line in your CUPS.CONF.
please provide emerge info
(i wan't to know your baselayout version)
Gentoo Base System version 1.4.3.10 Portage 2.0.49-r21 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r9, 2.4.20-gentoo-r5) ================================================================= System uname: 2.4.20-gentoo-r5 i686 Pentium III (Coppermine) ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium3 -O3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=pentium3 -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="berkdb crypt cups encode foomaticdb gdbm gpm gtk2 imlib innodb jpeg libg++ libwww mad mikmod mysql ncurses nls pam pcmcia perl python qtmt readline samba sdl slang spell ssl svga tcpd truetype x86 xml2 xmms xv zlib"
I have a similar problem that could be related. Cups was working fine until I upgraded glibc from version 2.3.2-r3 to 2.3.2-r9. After the upgrade, cupsd would not start and I get the message: CUPS Child exited with status 127! Rebuilding cups does not help, but after downgrading glibc back to 2.3.2-r3, cupsd will start without problems.
I don't think it is related. My problem was simple. CUPS was trying to start before the netowrk but it needed the network to run.
Cal: update to latest baselayout, run depscan.sh and reboot Steve: that not related, open another bug report
Cal: did that help?
The server in question is my road server. It won't be back in house until sometime after Easter. I'll know more then.