devd.conf revision 125366 
1# $FreeBSD: head/etc/devd.conf 125366 2004-02-03 04:18:56Z njl $
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, the name of this script it 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#
59# Rescan scsi device-names on attach, but not detach.
60#
61attach 0 {
62	device-name "$scsi-controller-regex";
63	action "camcontrol rescan all";
64};
65
66# Don't even try to second guess what to do about drivers that don't
67# match here.  Instead, pass it off to syslog.  Commented out for the
68# moment, as pnpinfo isn't set in devd yet
69nomatch 0 {
70#	action "logger Unknown device: $pnpinfo $location $bus";
71};
72
73# Switch power profiles when the AC line state changes
74notify 10 {
75	match "system"		"ACPI";
76	match "subsystem"	"ACAD";
77	action "/etc/rc.d/power_profile $notify";
78};
79
80# Notify all users before beginning emergency shutdown when we get
81# a _CRT or _HOT thermal event and we're going to power down the system
82# very soon.
83notify 10 {
84	match "system"		"ACPI";
85	match "subsystem"	"Thermal";
86	match "notify"		"0xcc";
87	action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'";
88};
89
90/* EXAMPLES TO END OF FILE
91
92# The following might be an example of something that a vendor might
93# install if you were to add their device.  This might reside in
94# /usr/local/etc/devd/deqna.conf.  A deqna is, in this hypothetical
95# example, a pccard ethernet-like device.  Students of history may
96# know other devices by this name, and will get the in-jokes in this
97# entry.
98nomatch 10 {
99	match "bus" "pccard[0-9]+";
100	match "manufacturer" "0x1234";
101	match "product" "0x2323";
102	action "kldload if_deqna";
103};
104attach 10 {
105	device-name "deqna[0-9]+";
106	action "/etc/pccard_ether $device-name start";
107};
108detach 10 {
109	device-name "deqna[0-9]+";
110	action "/etc/pccard_ether $device-name stop";
111};
112
113# Examples of notify hooks.  A notify is a generic way for a kernel
114# subsystem to send event notification to userland.
115#
116# Here are some examples of ACPI notify handlers.  ACPI subsystems that
117# generate notifies include the AC adapter, power/sleep buttons,
118# control method batteries, lid switch, and thermal zones.
119#
120# Information returned is not always the same as the ACPI notify
121# events.  See the ACPI specification for more information about
122# notifies.  Here is the information returned for each subsystem:
123#
124# ACAD:		AC line state (0 is offline, 1 is online)
125# Button:	Button pressed (0 for power, 1 for sleep)
126# CMBAT:	ACPI battery events
127# Lid:		Lid state (0 is closed, 1 is open)
128# Thermal:	ACPI thermal zone events
129#
130# This example calls a script when the AC state changes, passing the
131# notify value as the first argument.  If the state is 0x00, it might
132# call some sysctls to implement economy mode.  If 0x01, it might set
133# the mode to performance.
134notify 10 {
135	match "system"		"ACPI";
136	match "subsystem"	"ACAD";
137	action			"/etc/acpi_ac $notify";
138};
139*/
140