Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 70 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

acpid




SYNOPSIS

       acpid [options]


DESCRIPTION

       acpid is designed to notify user-space  programs  of  ACPI
       events.   acpid  should be started during the system boot,
       and will run as a background process, by default.  It will
       open  an  events  file  (/proc/acpi/event  by default) and
       attempt to read whole lines.  When a line is received  (an
       event),  acpid  will  examine a list of rules, and execute
       the rules that match the event.

       Rules are defined by simple  configuration  files.   acpid
       will  look  in a configuration directory (/etc/acpi/events
       by default), and parse all files that do not begin with  a
       period  ('.').  Each file must define two things: an event
       and an action.  Any blank lines, or lines where the  first
       character  is  a pound sign ('#') are ignored.  Extraneous
       lines are flagged as warnings, but are  not  fatal.   Each
       line  has three tokens: the key, a literal equal sign, and
       the value.  The key can be up to  63  characters,  and  is
       case-insensitive  (but whitespace matters).  The value can
       be up to 511 characters, and is case and whitespace sensi­
       tive.

       The  event value is a regular expression (see regcomp(3)),
       against which events are matched.

       The action value is a commandline, which will  be  invoked
       via  /bin/sh  whenever an event matching the rule in ques­
       tion occurs.  The commandline  may  include  shell-special
       characters,  and they will be preserved.  The only special
       characters in an action value are "%" escaped.  The string
       "%e" will be replaced by the literal text of the event for
       which the action was invoked.   This  string  may  contain
       spaces,  so  the  commandline  must take care to quote the
       "%e" if it wants a single token.  The string "%%" will  be
       replaced  by  a  literal  "%".   All other "%" escapes are
       reserved, and will cause a rule to not load.

       This feature allows multiple rules to be defined  for  the
       same  event (though no ordering is guaranteed), as well as
       one rule to be defined  for  multiple  events.   To  force
       acpid  to reload the rule configuration, send it a SIGHUP.

       In addition to rule files, acpid also accepts  connections
       on   a   UNIX   domain  socket  (/var/run/acpid.socket  by
       default).  Any application may  connect  to  this  socket.
       Once  connected,  acpid  will  send  the  text of all ACPI
       events to the client.  The client has  the  responsibility
                   acpid  looks  for  rule  configuration  files.
                   Default is /etc/acpi/events.

       -d, --debug This option increases the acpid debug level by
                   one.   If  the  debug level is non-zero, acpid
                   will run in the foreground, and  will  log  to
                   stdout/stderr, rather than a log file.

       -e, --eventfile filename
                   This  option changes the event file from which
                   acpid    reads     events.      Default     is
                   /proc/acpi/event.

       -g, --socketgroup groupname
                   This option changes the group ownership of the
                   UNIX domain socket to  which  acpid  publishes
                   events.

       -l, --logfile filename
                   This  option  changes  the  log  file to which
                   acpid writes.  Default is /var/log/acpid.

       -m, --socketmode mode
                   This option changes  the  permissions  of  the
                   UNIX  domain  socket  to which acpid publishes
                   events.  Default is 0666.

       -s, --socketfile filename
                   This option  changes  the  name  of  the  UNIX
                   domain  socket  which acpid opens.  Default is
                   /var/run/acpid.socket.

       -S, --nosocket filename
                   This option tells acpid not  to  open  a  UNIX
                   domain  socket.  This overrides the -s option,
                   and negates all other socket options.

       -v, --version
                   Print version information and exit.

       -h, --help  Show help and exit.


EXAMPLE

       This example - placed  in  /etc/acpi/events/power  -  will
       shut down your system if you press the power button.

       event=button power.*
       action=/usr/local/sbin/power.sh "%e"

       The  script power.sh gets called and will see the complete
       event string as parameter $1.

       below.


SEE ALSO

       regcomp(3), sh(1), socket(2), connect(2)


AUTHORS

       Andrew Grover <andrew.grover@intel.com>
       Tim Hockin <thockin@sun.com>
       Cajus Pollmeier <pollmeier@gonicus.de>

                           August 2001                   acpid(8)
  




Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds