devd.conf revision 134584 
1# $FreeBSD: head/etc/devd.conf 134584 2004-09-01 00:08:15Z brooks $
2#
3# Refer to devd.conf(5) and devd(8) man pages for the details on how to
4# run and configure devd.
5#
6
7# NB: All regular expressions have an implicit ^$ around them.
8# NB: device-name is shorthand for 'match device-name'
9
10options {
11	# Each directory directive adds a directory the list of directories
12	# that we scan for files.  Files are read-in in the order that they
13	# are returned from readdir(3).  The rule-sets are combined to
14	# create a DFA that's used to match events to actions.
15	directory "/etc/devd";
16	directory "/usr/local/etc/devd";
17	pid-file "/var/run/devd.pid";
18
19	# Setup some shorthand for regex that we use later in the file.
20	set ethernet-nic-regex
21		"(an|ar|ath|aue|awi|bfe|bge|cm|cnw|cs|cue|dc|de|ed|el|em|ep|\
22		ex|fe|fxp|gem|gx|hme|ie|kue|lge|lnc|my|nge|pcn|ray|re|rl|rue|\
23		sf|sis|sk|sn|snc|ste|ti|tl|tx|txp|vr|vx|wb|wi|xe|xl)[0-9]+";
24	set scsi-controller-regex
25		"(adv|advw|aic|aha|ahb|ahc|ahd|bt|ct|iir|isp|mly|mpt|ncv|nsp|\
26		stg|sym|wds)[0-9]+";
27};
28
29# Note that the attach/detach with the highest value wins, so that one can
30# override these general rules.
31
32#
33# For ethernet like devices, the default is to run dhclient.  Due to
34# a historical accident, this script is called pccard_ether.
35#
36attach 0 {
37	device-name "$ethernet-nic-regex";
38	action "/etc/pccard_ether $device-name start";
39};
40
41detach 0 {
42	device-name "$ethernet-nic-regex";
43	action "/etc/pccard_ether $device-name stop";
44};
45
46# An entry like this might be in a different file, but is included here
47# as an example of how to override things.  Normally 'ed50' would match
48# the above attach/detach stuff, but the value of 100 makes it
49# ed50 is hard wired to 1.2.3.4
50attach 100 {
51	device-name "ed50";
52	action "ifconfig $device-name inet 1.2.3.4 netmask 0xffff0000";
53};
54detach 100 {
55	device-name "ed50";
56};
57
58# When a USB keyboard arrives, attach it as the console keyboard
59attach 100 {
60	device-name "ukbd0";
61	action "test -c /dev/kbd1 && kbdcontrol -k /dev/kbd1 < /dev/console";
62};
63detach 100 {
64	device-name "ukbd0";
65	action "kbdcontrol -k /dev/kbd0 < /dev/console";
66};
67
68#
69# Rescan scsi device-names on attach, but not detach.
70#
71attach 0 {
72	device-name "$scsi-controller-regex";
73//	action "camcontrol rescan all";
74};
75
76# Don't even try to second guess what to do about drivers that don't
77# match here.  Instead, pass it off to syslog.  Commented out for the
78# moment, as pnpinfo isn't set in devd yet
79nomatch 0 {
80#	action "logger Unknown device: $pnpinfo $location $bus";
81};
82
83# Switch power profiles when the AC line state changes
84notify 10 {
85	match "system"		"ACPI";
86	match "subsystem"	"ACAD";
87	action "/etc/rc.d/power_profile $notify";
88};
89
90# Notify all users before beginning emergency shutdown when we get
91# a _CRT or _HOT thermal event and we're going to power down the system
92# very soon.
93notify 10 {
94	match "system"		"ACPI";
95	match "subsystem"	"Thermal";
96	match "notify"		"0xcc";
97	action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'";
98};
99
100/* EXAMPLES TO END OF FILE
101
102# The following might be an example of something that a vendor might
103# install if you were to add their device.  This might reside in
104# /usr/local/etc/devd/deqna.conf.  A deqna is, in this hypothetical
105# example, a pccard ethernet-like device.  Students of history may
106# know other devices by this name, and will get the in-jokes in this
107# entry.
108nomatch 10 {
109	match "bus" "pccard[0-9]+";
110	match "manufacturer" "0x1234";
111	match "product" "0x2323";
112	action "kldload if_deqna";
113};
114attach 10 {
115	device-name "deqna[0-9]+";
116	action "/etc/pccard_ether $device-name start";
117};
118detach 10 {
119	device-name "deqna[0-9]+";
120	action "/etc/pccard_ether $device-name stop";
121};
122
123# Examples of notify hooks.  A notify is a generic way for a kernel
124# subsystem to send event notification to userland.
125#
126# Here are some examples of ACPI notify handlers.  ACPI subsystems that
127# generate notifies include the AC adapter, power/sleep buttons,
128# control method batteries, lid switch, and thermal zones.
129#
130# Information returned is not always the same as the ACPI notify
131# events.  See the ACPI specification for more information about
132# notifies.  Here is the information returned for each subsystem:
133#
134# ACAD:		AC line state (0 is offline, 1 is online)
135# Button:	Button pressed (0 for power, 1 for sleep)
136# CMBAT:	ACPI battery events
137# Lid:		Lid state (0 is closed, 1 is open)
138# Thermal:	ACPI thermal zone events
139#
140# This example calls a script when the AC state changes, passing the
141# notify value as the first argument.  If the state is 0x00, it might
142# call some sysctls to implement economy mode.  If 0x01, it might set
143# the mode to performance.
144notify 10 {
145	match "system"		"ACPI";
146	match "subsystem"	"ACAD";
147	action			"/etc/acpi_ac $notify";
148};
149*/
150