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