Summary: | app-admin/metalog - Support for metalog inside VServers | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Adrian Perez <adrian+gentoo> |
Component: | [OLD] Server | Assignee: | SpanKY <vapier> |
Status: | RESOLVED UPSTREAM | ||
Severity: | enhancement | CC: | base-system, Dessa |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
URL: | https://sourceforge.net/tracker/index.php?func=detail&aid=1751757&group_id=30635&atid=399902 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | metalog-0.8-disable-klog.patch |
Description
Adrian Perez
2007-07-11 09:25:21 UTC
Created attachment 124535 [details, diff]
metalog-0.8-disable-klog.patch
I have attached a patch which adds a "--no-kernel" (or simply "-N") command line flag which disables spawning the kernel log instance of metalog, thus disabling reading of messages from the kernel.
With this patch you can run metalog inside an VServer, by adding "--no-kernel" to METALOG_OPTS in /etc/conf.d/metalog
I have also submitted the patch upstream (I filled a bug in the SF project page for metalog).
I've done this ok with sysklog. be nice if they were split though. klog logs at startup then no more logging. Also I installed from a stage3 of 2006.0 and am trying to update. The kernel of the machine underneath can be gotten with uname -a of course but gentoo wants to install the headers if you do more than glsa-check -f accepted. Other issues portage complains of no support for my arch. >>> Install portage-2.1.4.4 into /var/tmp/portage/sys-apps/portage-2.1.4.4/image/ categ ory sys-apps * * Portage does not have an arch-specific configuration for this arch. * Please notify the arch maintainer about this issue. Using generic. * >>> Completed installing portage-2.1.4.4 into /var/tmp/portage/sys-apps/portage-2.1.4.4 /image/ I'll file a new bug if you wish. |