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 quietstart $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 quietstart $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 quietstart $device-name";
97 device-name "ubt[0-9]+";
98 action "/etc/rc.d/bluetooth quietstop $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";
112 device-name "ums[0-9]+";
113 action "/etc/rc.d/moused quietstart $device-name";
117 device-name "ums[0-9]+";
118 action "/etc/rc.d/moused stop $device-name";
121 # Firmware download into the ActiveWire board. After the firmware download is
122 # done the device detaches and reappears as something new and shiny
125 match "vendor" "0x0854";
126 match "product" "0x0100";
127 match "release" "0x0000";
128 action "/usr/local/bin/ezdownload -f /usr/local/share/usb/firmware/0854.0100.0_01.hex $device-name";
131 # Firmware download for Entrega Serial DB25 adapter.
133 match "vendor" "0x1645";
134 match "product" "0x8001";
135 match "release" "0x0101";
136 action "if ! kldstat -n usio > /dev/null 2>&1 ; then kldload usio; fi /usr/sbin/ezdownload -v -f /usr/share/usb/firmware/1645.8001.0101 /dev/$device-name";
139 # This entry starts the ColdSync tool in daemon mode. Make sure you have an up
140 # to date /usr/local/etc/palms. We override the 'listen' settings for port and
141 # type in /usr/local/etc/coldsync.conf.
143 device-name "ugen[0-9]+";
144 match "vendor" "0x082d";
145 match "product" "0x0100";
146 match "release" "0x0100";
147 action "/usr/local/bin/coldsync -md -p /dev/$device-name -t usb";
151 # Rescan scsi device-names on attach, but not detach. However, it is
152 # disabled by default due to reports of problems.
155 device-name "$scsi-controller-regex";
156 // action "camcontrol rescan all";
159 # Don't even try to second guess what to do about drivers that don't
160 # match here. Instead, pass it off to syslog. Commented out for the
161 # moment, as the pnpinfo variable isn't set in devd yet. Individual
162 # variables within the bus supplied pnpinfo are set.
164 # action "logger Unknown device: $pnpinfo $location $bus";
167 # Various logging of unknown devices.
169 match "bus" "uhub[0-9]+";
170 action "logger Unknown USB device: vendor $vendor product $product \
174 # Some PC-CARDs don't offer numerical manufacturer/product IDs, just
175 # show the CIS info there.
177 match "bus" "pccard[0-9]+";
178 match "manufacturer" "0xffffffff";
179 match "product" "0xffffffff";
180 action "logger Unknown PCCARD device: CISproduct $cisproduct \
181 CIS-vendor $cisvendor bus $bus";
185 match "bus" "pccard[0-9]+";
186 action "logger Unknown PCCARD device: manufacturer $manufacturer \
187 product $product CISproduct $cisproduct CIS-vendor \
188 $cisvendor bus $bus";
192 match "bus" "cardbus[0-9]+";
193 action "logger Unknown Cardbus device: device $device class $class \
194 vendor $vendor bus $bus";
197 # Switch power profiles when the AC line state changes.
199 match "system" "ACPI";
200 match "subsystem" "ACAD";
201 action "/etc/rc.d/power_profile $notify";
204 # Notify all users before beginning emergency shutdown when we get
205 # a _CRT or _HOT thermal event and we're going to power down the system
208 match "system" "ACPI";
209 match "subsystem" "Thermal";
210 match "notify" "0xcc";
211 action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'";
214 # Sample ZFS problem reports handling.
216 match "system" "ZFS";
217 match "type" "zpool";
218 action "logger -p kern.err 'ZFS: failed to load zpool $pool'";
222 match "system" "ZFS";
224 action "logger -p kern.err 'ZFS: vdev failure, zpool=$pool type=$type'";
228 match "system" "ZFS";
230 action "logger -p kern.warn 'ZFS: zpool I/O failure, zpool=$pool error=$zio_err'";
234 match "system" "ZFS";
236 action "logger -p kern.warn 'ZFS: vdev I/O failure, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size error=$zio_err'";
240 match "system" "ZFS";
241 match "type" "checksum";
242 action "logger -p kern.warn 'ZFS: checksum mismatch, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size'";
245 # User requested suspend, so perform preparation steps and then execute
246 # the actual suspend process.
248 match "system" "ACPI";
249 match "subsystem" "Suspend";
250 action "/etc/rc.suspend acpi $notify";
253 match "system" "ACPI";
254 match "subsystem" "Resume";
255 action "/etc/rc.resume acpi $notify";
258 # The next blocks enable volume hotkeys that can be found on the Asus EeePC
260 match "system" "ACPI";
261 match "subsystem" "ASUS-Eee";
262 match "notify" "0x13";
267 match "system" "ACPI";
268 match "subsystem" "ASUS-Eee";
269 match "notify" "0x14";
270 action "mixer vol -10";
274 match "system" "ACPI";
275 match "subsystem" "ASUS-Eee";
276 match "notify" "0x15";
277 action "mixer vol +10";
280 /* EXAMPLES TO END OF FILE
282 # The following might be an example of something that a vendor might
283 # install if you were to add their device. This might reside in
284 # /usr/local/etc/devd/deqna.conf. A deqna is, in this hypothetical
285 # example, a pccard ethernet-like device. Students of history may
286 # know other devices by this name, and will get the in-jokes in this
289 match "bus" "pccard[0-9]+";
290 match "manufacturer" "0x1234";
291 match "product" "0x2323";
292 action "kldload if_deqna";
295 device-name "deqna[0-9]+";
296 action "/etc/pccard_ether $device-name start";
299 device-name "deqna[0-9]+";
300 action "/etc/pccard_ether $device-name stop";
303 # Examples of notify hooks. A notify is a generic way for a kernel
304 # subsystem to send event notification to userland.
306 # Here are some examples of ACPI notify handlers. ACPI subsystems that
307 # generate notifies include the AC adapter, power/sleep buttons,
308 # control method batteries, lid switch, and thermal zones.
310 # Information returned is not always the same as the ACPI notify
311 # events. See the ACPI specification for more information about
312 # notifies. Here is the information returned for each subsystem:
314 # ACAD: AC line state (0 is offline, 1 is online)
315 # Button: Button pressed (0 for power, 1 for sleep)
316 # CMBAT: ACPI battery events
317 # Lid: Lid state (0 is closed, 1 is open)
318 # Suspend, Resume: Suspend and resume notification
319 # Thermal: ACPI thermal zone events
321 # This example calls a script when the AC state changes, passing the
322 # notify value as the first argument. If the state is 0x00, it might
323 # call some sysctls to implement economy mode. If 0x01, it might set
324 # the mode to performance.
326 match "system" "ACPI";
327 match "subsystem" "ACAD";
328 action "/etc/acpi_ac $notify";