3 # Refer to devd.conf(5) and devd(8) man pages for the details on how to
4 # run and configure devd.
7 # NB: All regular expressions have an implicit ^$ around them.
8 # NB: device-name is shorthand for 'match device-name'
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";
19 # Setup some shorthand for regex that we use later in the file.
20 #XXX Yes, these are gross -- imp
21 set scsi-controller-regex
22 "(aac|adv|adw|aha|ahb|ahc|ahd|aic|amd|amr|asr|bt|ciss|ct|dpt|\
23 esp|ida|iir|ips|isp|mlx|mly|mpt|ncr|ncv|nsp|stg|sym|trm|wds)\
27 # Note that the attach/detach with the highest value wins, so that one can
28 # override these general rules.
31 # Configure the interface on attach. Due to a historical accident, this
32 # script is called pccard_ether.
35 match "system" "IFNET";
36 match "type" "ATTACH";
37 action "/etc/pccard_ether $subsystem start";
41 match "system" "IFNET";
42 match "type" "DETACH";
43 action "/etc/pccard_ether $subsystem stop";
47 # Try to start dhclient on Ethernet like interfaces when the link comes
48 # up. Only devices that are configured to support DHCP will actually
49 # run it. No link down rule exists because dhclient automaticly exits
50 # when the link goes down.
53 match "system" "IFNET";
54 match "type" "LINK_UP";
55 media-type "ethernet";
56 action "/etc/rc.d/dhclient start $subsystem";
60 # Like Ethernet devices, but separate because
61 # they have a different media type. We may want
62 # to exploit this later.
66 action "/etc/pccard_ether $device-name stop";
70 action "/etc/pccard_ether $device-name start";
73 match "system" "IFNET";
74 match "type" "LINK_UP";
76 action "/etc/rc.d/dhclient start $subsystem";
79 # An entry like this might be in a different file, but is included here
80 # as an example of how to override things. Normally 'ed50' would match
81 # the above attach/detach stuff, but the value of 100 makes it
82 # hard wired to 1.2.3.4.
85 action "ifconfig $device-name inet 1.2.3.4 netmask 0xffff0000";
91 # When a USB Bluetooth dongle appears activate it
93 device-name "ubt[0-9]+";
94 action "/etc/rc.d/bluetooth start $device-name";
97 device-name "ubt[0-9]+";
98 action "/etc/rc.d/bluetooth stop $device-name";
101 # When a USB keyboard arrives, attach it as the console keyboard.
104 action "/etc/rc.d/syscons setkeyboard /dev/ukbd0";
108 action "/etc/rc.d/syscons setkeyboard /dev/kbd0";
111 # The entry below starts moused when a mouse is plugged in. Moused
112 # stops automatically (actually it bombs :) when the device disappears.
114 device-name "ums[0-9]+";
115 action "/etc/rc.d/moused start $device-name";
119 # Rescan scsi device-names on attach, but not detach. However, it is
120 # disabled by default due to reports of problems.
123 device-name "$scsi-controller-regex";
124 // action "camcontrol rescan all";
127 # Don't even try to second guess what to do about drivers that don't
128 # match here. Instead, pass it off to syslog. Commented out for the
129 # moment, as pnpinfo isn't set in devd yet.
131 # action "logger Unknown device: $pnpinfo $location $bus";
134 # Switch power profiles when the AC line state changes.
136 match "system" "ACPI";
137 match "subsystem" "ACAD";
138 action "/etc/rc.d/power_profile $notify";
141 # Notify all users before beginning emergency shutdown when we get
142 # a _CRT or _HOT thermal event and we're going to power down the system
145 match "system" "ACPI";
146 match "subsystem" "Thermal";
147 match "notify" "0xcc";
148 action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'";
151 /* EXAMPLES TO END OF FILE
153 # The following might be an example of something that a vendor might
154 # install if you were to add their device. This might reside in
155 # /usr/local/etc/devd/deqna.conf. A deqna is, in this hypothetical
156 # example, a pccard ethernet-like device. Students of history may
157 # know other devices by this name, and will get the in-jokes in this
160 match "bus" "pccard[0-9]+";
161 match "manufacturer" "0x1234";
162 match "product" "0x2323";
163 action "kldload if_deqna";
166 device-name "deqna[0-9]+";
167 action "/etc/pccard_ether $device-name start";
170 device-name "deqna[0-9]+";
171 action "/etc/pccard_ether $device-name stop";
174 # Examples of notify hooks. A notify is a generic way for a kernel
175 # subsystem to send event notification to userland.
177 # Here are some examples of ACPI notify handlers. ACPI subsystems that
178 # generate notifies include the AC adapter, power/sleep buttons,
179 # control method batteries, lid switch, and thermal zones.
181 # Information returned is not always the same as the ACPI notify
182 # events. See the ACPI specification for more information about
183 # notifies. Here is the information returned for each subsystem:
185 # ACAD: AC line state (0 is offline, 1 is online)
186 # Button: Button pressed (0 for power, 1 for sleep)
187 # CMBAT: ACPI battery events
188 # Lid: Lid state (0 is closed, 1 is open)
189 # Thermal: ACPI thermal zone events
191 # This example calls a script when the AC state changes, passing the
192 # notify value as the first argument. If the state is 0x00, it might
193 # call some sysctls to implement economy mode. If 0x01, it might set
194 # the mode to performance.
196 match "system" "ACPI";
197 match "subsystem" "ACAD";
198 action "/etc/acpi_ac $notify";