Metalog won't run inside a VServer because it tries to read kernel logs, which is impossible inside a virtual machine. Reproducible: Always Steps to Reproduce: 1. Install VServer and create a virtual machine 2. Install app-admin/metalog inside the virtual machine 3. Run "metalog -v" as root Actual Results: Metalog does not work and prints the following error: Unable to control the kernel logging device: Operation not permitted Unable to bind sockets - aborting Expected Results: It would be nice if Metalog could run inside VServer virtual machines.
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.
