I installed a stage3 tarball, and like in the PPC version, bug 6537, I installed a syslog-ng, only to find out that sysklogd was installed and was blocking the use of syslog-ng. Also, I found out that a version of cron was also installed because /etc/cron.daily and such were present. Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: Please explain that stage3 does not need a syslogger or cron.
Releng, can you confirm that stage3 now contains a system logger and cron daemon by default? If so, could this be removed again in the future stage3's? They kinda "force" people onto a certain system logger/cron daemon, and even worse, cron daemons are optional (one can live without). Also, how can I confirm this myself in the near future? What files of catalyst are used for this (cvs location?)
Bleh, okay, apparently we do force it now. I'll temporarily add a warning to the docs, but this shouldn't happen in the future! Releng team: Unless I'm mistaken, I don't think we need to have a default system logger in stage3 - users like choices (sysklogd, metalogd, syslog-ng, ...) and don't want us to "force" one upon them. There is no default cron though, only cronbase (which can stay in the tarball if you want, although it's not necessary).
I'm removing docs-team@ from cc. The documentation has been altered, it's up to the releng team now.
..and you're 100% positive that you did not install a package or make a USE flag change that pulled in a package that had a dependency on a logger? # find -type d | sort | grep sysklogd # find -type d | sort | grep cron ./sys-process/cronbase-0.3.2 At any rate, I have no "real" information here. Which tarball did you use, exactly? I'm inclined to mark this one as INVALID. As I can verify without a shadow of a doubt that there is neither a system logger, nor a cron daemon in the stage3 tarball for 2005.1 for x86.
Timeout
