Maybe there's a dependency issue or something going on here. I realize now that with syslog-ng already installed and operating, I should not have emerged sysklogd as it is just another package that does much the same thing. At the time, I thought that it did additional logging of kernel messages not done by syslog-ng. Now I think I just need to do more configuration of syslog-ng so that it captures those other kernel log messages (it doesn't in a default installation/configuration). Anyway, I did do the above. That is: emerge -v syslog-ng rc-update add syslog-ng default emerge -v sysklogd then I realized my mistake and unmerged sysklogd emerge -v unmerge sysklogd At this point, the "Caching service dependencies..." message at the end of this and every subsequent emerge always included something along the lines of: Service 'sysklogd' already provides 'logging'!; Not adding service 'syslog-ng'... Now, I'm not really sure what the implications of this message are, but it didn't look right to me. So I googled and found http://www.parseerror.com/errors/vixie-cron-vs-vcron.txt and that gave me clues on resolving the problem. Content of this URL pasted below. You type: emerge <whatever> You get: ... * Caching service dependencies... * Service 'vcron' already provide 'cron'!; * Not adding service 'vixie-cron'... [ ok ] * Caching service dependencies... * Service 'vcron' already provide 'cron'!; * Not adding service 'vixie-cron'... [ ok ] ... Problem: There is a naming conflict with the packages, I think vcron was officially renamed to vixie-cron because Mr. Vixie's ego was hurting and/or he wanted to just make us type more. Anyhow... There are a bunch of posts on gentoo forums about this, this one has links to the others: http://forums.gentoo.org/viewtopic.php?t=121455 Solution: Basically we need to get rid of vcron. As root: /etc/init.d/vcron stop emerge unmerge vcron rc-update del vcron rm /etc/init.d/vcron rc-update add vixie-cron default /etc/init.d/vixie-cron start Verify: You shouldn't get the message anymore :P Instead, I did the following: /etc/init.d/sysklogd stop (it wasn't running to begin with but...) emerge unmerge sysklogd (actually, I had already done this, and I didn't do it again) rc-update del sysklogd (it wasn't present in the first place but...) rm /etc/init.d/sysklogd (this file was there and I removed it which seems to have been the resolution of the problem) rc-update add syslog-ng default (already there) /etc/init.d/syslog-ng start (already running) and hereafter, I didn't get the odd "Caching service dependencies..." messages that mentioned sysklogd blocking syslog-ng and so forth. Reproducible: Always Steps to Reproduce: 1. I only really tried it once 2. See above in details 3. Actual Results: See above in details Expected Results: See above in details tombstone root # emerge info Portage 2.0.50-r6 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 2.4.25-gentoo-r2) ================================================================= System uname: 2.4.25-gentoo-r2 i686 Intel(R) Xeon(TM) CPU 2.40GHz Gentoo Base System version 1.4.9 distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/afs/C /etc/afs/afsws /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="http://128.213.5.34/gentoo/ http://mirror.datapipe.net/gentoo ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://gentoo.eliteitminds.com" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X Xaw3d acl acpi afs alsa apache2 apm arts avi berkdb bonobo caps crypt cups doc emacs emacs-w3 encode esd ethereal evo firebird flac foomaticdb gdbm gif gnome gpm gstreamer gtk gtk2 gtkhtml guile hardened icq imagemagick imap imlib innodb ipv6 jabber jack java jikes jpeg kde kerberos krb4 ldap libg++ libwww mad mcal mikmod motif mozilla mpeg mysql ncurses nls odbc oggvorbis opengl oss pam pda pdflib perl plotutils png ppds prelude python qt quicktime readline ruby samba sasl sdl slang slp spell sse ssl svga tcltk tcpd tetex tiff truetype unicode usb vhosts x86 xinerama xml2 xmms xv zeo zlib"
I had a similar problem. Had syslog-ng, was moving to metalog & it kept saying Service syslog-ng already provides syslog (after I had unmerged syslog-ng). After I manually removed /etc/init.d/syslog-ng, everything was fine. Is this correct functionality? I guess unmerging should remove the stuff in /etc/init.d/ as well? Or if that's cfgproed then should tell the user what's going on...
there are no real implications; the warning is mostly for show if you just `rc-update del sysklogd ; rc-udpate add syslog-ng default` everything will be ok *** This bug has been marked as a duplicate of 60688 ***
