Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 18394 Details for
Bug 29600
Metalog a good recommendation ?
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
[patch]
Patch 1/2: (installation guide) same as before plus a small note about the FAQ
gentoo-x86-install.diff-no_metalogd_per_default (text/plain), 1.98 KB, created by
Sven Vermeulen (RETIRED)
on 2003-09-27 05:31:46 UTC
(
hide
)
Description:
Patch 1/2: (installation guide) same as before plus a small note about the FAQ
Filename:
MIME Type:
Creator:
Sven Vermeulen (RETIRED)
Created:
2003-09-27 05:31:46 UTC
Size:
1.98 KB
patch
obsolete
>--- ../cvs/htdocs/doc/en/gentoo-x86-install.xml 2003-09-24 09:50:01.000000000 +0200 >+++ gentoo-x86-install.xml 2003-09-27 14:26:05.000000000 +0200 >@@ -2242,11 +2242,9 @@ > Your new custom kernel (and modules) are now installed. Now you need to choose > a system logger that you would like to install. We offer sysklogd, which is > the traditional set of system logging daemons. We also have msyslog and >-syslog-ng as well as metalog. Power users seem to gravitate away from >-sysklogd (not very good performance) and towards the newer alternatives. >-If in doubt, you may want to try metalog, since it seems to be quite popular. >-To merge your logger of choice, type <e>one</e> of the next four command >-sets: >+syslog-ng as well as metalog. If in doubt, you may want to try >+syslog-ng, since it is very flexible and feature-rich. To merge your logger of >+choice, type <e>one</e> of the next four command sets: > </p> > > <pre caption="Emerging System Logger of Choice"> >@@ -2264,21 +2262,7 @@ > </pre> > > <impo> >-Metalog flushes output to the disk in blocks, so messages aren't immediately >-recorded into the system logs. If you are trying to debug a daemon, this >-performance-enhancing behavior is less than helpful. When your Gentoo Linux >-system is up and running, you can send metalog a USR1 signal to temporarily >-turn off this message buffering (meaning that <c>tail -f >-<path>/var/log/everything/current</path></c> will now work in real time, as >-expected) and a USR2 signal to turn buffering back on again. If you want to >-disable buffering permanently, you can change METALOG_OPTS="-B" to >-METALOG_OPTS="-B -s" in <path>/etc/conf.d/metalog</path>. >-<pre caption="Turning metalog buffering on/off"> >-<codenote>To turn the buffering off:</codenote> >-# <i>killall -USR1 metalog</i> >-<codenote>To turn the buffering back on:</codenote> >-# <i>killall -USR2 metalog</i> >-</pre> >+If you chose <c>metalogd</c>, please read <uri link="faq.xml#doc_chap6_sect3">this FAQ</uri> on metalogd's buffering. > </impo> > > <p>
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 29600
:
18353
|
18354
| 18394