Bug 58665 – x86 guide gives 2 loggers and 2 crons

• Product: Gentoo Release Media
• Status: RESOLVED INVALID

[Description Michael Forbes 2004-07-28 08:24:40 UTC]

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.

[Comment 1 Sven Vermeulen (RETIRED) 2004-07-30 04:26:12 UTC]

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?)

[Comment 2 Sven Vermeulen (RETIRED) 2004-07-31 04:22:21 UTC]

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).

[Comment 3 Sven Vermeulen (RETIRED) 2004-10-09 05:44:58 UTC]

I'm removing docs-team@ from cc. The documentation has been altered, it's up to the releng team now.

[Comment 4 Chris Gianelloni (RETIRED) 2005-11-03 06:54:31 UTC]

..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.

[Comment 5 Xavier Neys (RETIRED) 2005-11-17 09:28:31 UTC]

Timeout