Bug 46835 – after upgrade to syslog-ng - Service 'sysklogd' already provide 'logger'!;

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Aben Siatris 2004-04-05 02:39:37 UTC]

>>> original instance of package unmerged safely.
 * As of syslog-ng-1.6.0_rc1-r1, this ebuild now installs a
 * default configuration instead of a sample configuration.  It
 * should now be usable out of the box.
 * To convert your existing syslog.conf for use with syslog-ng,
 * use the syslog2ng script in /usr/share/doc/syslog-ng-1.6.0_rc3-r1.
 * Caching service dependencies...
 *  Service 'sysklogd' already provide 'logger'!;
 *  Not adding service 'syslog-ng'...
>>> app-admin/syslog-ng-1.6.0_rc3-r1 merged.

>>> clean: No packages selected for removal.

>>> Auto-cleaning packages ...

>>> No outdated packages were found on your system.


 * GNU info directory index is up-to-date.


Reproducible: Always
Steps to Reproduce:
1.emerge syslog-ng
2.
3.




Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.4-rc1-love2)
=================================================================
System uname: 2.6.4-rc1-love2 i686 Intel(R) Celeron(TM) CPU                1300MHz
Gentoo Base System version 1.4.3.13
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=pentium3 -mcpu=pentium3 -fomit-frame-pointer
-fprefetch-loop-arrays -ffast-math -fforce-addr -falign-functions=4
-fprefetch-loop-arrays -funroll-loops -pipe -msse -mmmx"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=pentium3 -mcpu=pentium3 -fomit-frame-pointer
-fprefetch-loop-arrays -ffast-math -fforce-addr -falign-functions=4
-fprefetch-loop-arrays -funroll-loops -pipe -msse -mmmx"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="ftp://gentoo.inode.at/source/ http://gentoo.inode.at/
http://mirrors.sec.informatik.tu-darmstadt.de/gentoo
http://212.219.247.18/sites/www.ibiblio.org/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X aalib acl alsa apm arts avantgo avi berkdb bindist bonobo cdr cjk crypt
cups curl dga directfb dvb dvd encode esd fbcon flash foomaticdb gdbm ggi gif
gnome gpm gtk gtk2 gtkhtml guile icc imlib innodb java javascript jpeg kde
libg++ libwww mad maildir mikmod mmx motif mpeg nas ncurses nls nv nvidia odbc
oggvorbis opengl oss pam pda pdflib perl png python qt quicktime readline ruby
samba sdl slang spell sse ssl svga tcltk tcpd threads tiff truetype x86 xkb xml
xml2 xmms xv zlib"

[Comment 1 Tony Vroon (RETIRED) 2004-04-05 04:43:22 UTC]

You can fix this by removing /etc/init.d/sysklogd, even if you unmerge a package, it's initscript will not be wiped out (and it has a provide=logger).

[Comment 2 Aben Siatris 2004-04-05 04:57:13 UTC]

ok, thanx :)

[Comment 3 Georgi Georgiev 2004-11-23 04:52:35 UTC]

Comment #1 is actually a workaround and not a solution to the problem, isn't it?

Isn't this bug a real shortcoming of the current implementation of the initscripts?

If a runscript requires 'logger' (as this example is), shouldn't it instead of requiring the first one it finds (which usually is the first one in alphabetical order), first check if there is a script in some runlevel that provides the feature. So that someone can do

# rc-update del metalog
# rc-update del sysklogd
# rc-update add syslog-ng default
# depscan.sh

And then at boot, not have metalog started by iptables (for example), but syslog-ng.

If you cannot have more than one logger installed, because always the first one is going to be started at boot, then it should be reflected in the .ebuild-s themselves, i.e. RDEPEND="!virtual/logger" or similar for every logger. But that would make changing the logger rather hard, as one would have to remove the old one first.