дядь, не злись, тупизна неискоренима :)

Ответ на комментарий MonaSax # да я не злюсь, но тупизна - пипец как последнее время выводит из себя, "поубывав бы"

sanjek65, а я фсё еще под вендосервером - у миня фря не понимает hw_acpi_toshiba

Ответ на комментарий MonaSax # а я говорил, пингвин, как-никак но под любое жалезо строицца, я вон до сих пор ровербук юзаю, и ничо;), а фря - это так, балафство и несурьёзность))))
ПС: Соляру хоть бы попробовала для экспириенса штоль:D

Ответ на комментарий sanjek65 # sanjek65, соляро меня испугало доками

Ответ на комментарий MonaSax # да не, проще и стройнее беркли-дистрибутед всех мастей, и там всё классика, уж сильных отличий от юникс/посикс утилит/синтаксиса там не найдёшь:D

Ответ на комментарий sanjek65 # sanjek65, ну тк я чо с ней и ношусь так - оно ж понятнее :D

Ответ на комментарий MonaSax # бсдя понятнее? О_О ничего стройнее systemV не видел пока
бсд-базед - от лукавого:P чистая имха(ниасилил)

Ответ на комментарий sanjek65 # sanjek65, по сравнению с вашими линупсами всякими - понятнее в n-дцать раз :)!!у неё хотя бы маны подробнее написаны!!

Ответ на комментарий MonaSax # :D Света, я покараю тебя, с благославления Патрега, за речи твои крамольные
/me задумался .... а разве в линуксах манов нет, или оне по кхмерски, или, например на банту написаны

Ответ на комментарий sanjek65 # sanjek65, сравни man acpi в линугзе и в рогатом :D

Ответ на комментарий MonaSax # а зачем? О_О
В Линуксе оно просто работает, и нефик в маны лезть:Р, ядро всё определяет, подхватывает траблов нет))))
а вообще, что непонятного?:
sanja@amigo:~$ man acpid
acpid(8) acpid(8)



NAME
acpid - Advanced Configuration and Power Interface event daemon

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 fit to a runparts style naming conven
tion. This means that files containing a dot and contain characters different from a-z and 0-9
would be ignored. Debian implementation differs at this point from standard acpid. 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 sensitive.

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 question 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 con
nected, acpid will send the text of all ACPI events to the client. The client has the respon
sibility of filtering for messages about which it cares. acpid will not close the client
socket except in the case of a SIGHUP or acpid exiting.

acpid will log all of its activities, as well as the stdout and stderr of any actions to sys
log.

All the default file and directories can be changed with commandline options.

OPTIONS
-c, --confdir directory
This option changes the directory in which acpid looks for rule configuration
files. Default is /etc/acpi/events.

-C, --clientmax number
This option changes the maximum number of non-root socket connections which can be
made to the acpid socket. Default is 256.

-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 stderr, in addition to the
regular syslog.

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

-f, --foreground
This option keeps acpid in the foreground by not forking at startup.


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

-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.

DEPENDENCIES
acpid should work on any linux kernel released since 2003.

FILES
/proc/acpi/event
/etc/acpi/
/var/run/acpid.socket

BUGS
There are no known bugs. To file bug reports, see AUTHORS below.

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

AUTHORS
Tim Hockin <thockin@hockin.org>




acpid(8)

Всё правильно. В интернет надо пускать только с удостоверением и после экзаменов.

Ответ на комментарий Sb0y # и предварительно отпиздить юзера, так, для профилактики.
ПС: опять от серёги приполз спаммессиндж, надо зобанеть родственничка:D