Difference between pages "Installing a Logger" and "Package:ACPI Daemon"

(Difference between pages)
 
 
Line 1: Line 1:
 
== Introduction ==
 
== Introduction ==
In case you ever need to view important system messages, it is a wise idea to install a system logger. System loggers create a log in ‘’/var/log’’ Several different loggers exist. Listed below are some of the more commonly used loggers:
+
==== What is acpi? ====
* '''Metalog''' - "Metalog is a modern replacement for syslogd and klogd. The logged messages can be dispatched according to their facility, urgency, program name and/or Perl-compatible regular expressions."
+
"In computing, the Advanced Configuration and Power Interface (ACPI) specification provides an open standard for device configuration and power management by the operating system." [(http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface Wikipedia)]
* '''Syslog-ng'''
+
* '''Rsyslog'''
+
  
== Installation and adding to runlevel ==
+
==== What is acpid? ====
To install a logger, run the following command:
+
"ACPID is a completely flexible, totally extensible daemon for delivering ACPI events. It listens on a file (/proc/acpi/event) and when an event occurs, executes programs to handle the event. The programs it executes are configured through a set of configuration files, which can be dropped into place by packages or by the admin." [(http://acpid.sourceforge.net/ acpid Sourceforge)]
<console>
+
# ##i## emerge --ask metalog
+
  
These are the packages that would be merged, in order:
+
== Preparing to install ==
 
+
==== Kernel configuration ====
Calculating dependencies... done!
+
[ebuild  N    ] app-admin/metalog-3-r1  USE="unicode" 353 kB
+
 
+
Total: 1 package (1 new), Size of downloads: 353 kB
+
Would you like to merge these packages? [Yes/No] # ##i## yes
+
  
 +
== Installing acpid ==
 +
==== Emerging ====
 +
To install acpid, run this command:
 +
<console>
 +
##r### ##b##emerge -av acpid
 
</console>
 
</console>
  
After installing the logger, we have to add its initialization script to RC’s default runlevel. The default runlevel, defined at /etc/runlevels/default, contains symbolic links to all system initialization scripts that are run by default. To add the logger to the runlevel and then start the logger, run the following:
+
==== Adding to rc ====
 +
After you have finished installing acpid, you may want to add it to the list of rc services to be started with your system at boot.
 
<console>
 
<console>
# ##i## rc-update add metalog default
+
##r### ##b##rc-update add acpid default
* service metalog added to runlevel default
+
# ##i## rc
+
* Starting metalog ...
+
 
</console>
 
</console>
 
+
Then, run the following to start rc:
== Stopping the service ==
+
If, for whatever reason, you need to stop a service manually, you can run its initialization script directly from /etc/init.d:
+
 
<console>
 
<console>
# ##i##/etc/init.d/metalog stop
+
##r### ##b##rc
* Stopping metalog ...
+
 
</console>
 
</console>
 
[[Category:System]]
 
[[Category:System]]

Revision as of 01:29, November 11, 2013

Introduction

What is acpi?

"In computing, the Advanced Configuration and Power Interface (ACPI) specification provides an open standard for device configuration and power management by the operating system." [(http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface Wikipedia)]

What is acpid?

"ACPID is a completely flexible, totally extensible daemon for delivering ACPI events. It listens on a file (/proc/acpi/event) and when an event occurs, executes programs to handle the event. The programs it executes are configured through a set of configuration files, which can be dropped into place by packages or by the admin." [(http://acpid.sourceforge.net/ acpid Sourceforge)]

Preparing to install

Kernel configuration

Installing acpid

Emerging

To install acpid, run this command:

# emerge -av acpid

Adding to rc

After you have finished installing acpid, you may want to add it to the list of rc services to be started with your system at boot.

# rc-update add acpid default

Then, run the following to start rc:

# rc