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 to the list of
12 # directories that we scan for files. Files are loaded in the order
13 # that they are returned from readdir(3). The rule-sets are combined
14 # to 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.
34 # NB: DETACH events are ignored; the kernel should handle all cleanup
35 # (routes, arp cache). Beware of races against immediate create
36 # of a device with the same name; e.g.
37 # ifconfig bridge0 destroy; ifconfig bridge0 create
40 match "system" "IFNET";
41 match "subsystem" "!usbus[0-9]+";
42 match "type" "ATTACH";
43 action "/etc/pccard_ether $subsystem start";
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 automatically 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 # Firmware downloader for Atheros AR3011 based USB Bluetooth devices
103 # match "vendor" "0x0cf3";
104 # match "product" "0x3000";
105 # action "sleep 2 && /usr/sbin/ath3kfw -d $device-name -f /usr/local/etc/ath3k-1.fw";
108 # When a USB keyboard arrives, attach it as the console keyboard.
111 action "/etc/rc.d/syscons setkeyboard /dev/ukbd0";
115 action "/etc/rc.d/syscons setkeyboard /dev/kbd0";
119 match "system" "DEVFS";
120 match "subsystem" "CDEV";
121 match "type" "CREATE";
122 match "cdev" "ums[0-9]+";
124 action "/etc/rc.d/moused quietstart $cdev";
128 match "system" "DEVFS";
129 match "subsystem" "CDEV";
130 match "type" "DESTROY";
131 match "cdev" "ums[0-9]+";
133 action "/etc/rc.d/moused stop $cdev";
136 # Firmware download into the ActiveWire board. After the firmware download is
137 # done, the device detaches and reappears as something new and shiny
140 match "vendor" "0x0854";
141 match "product" "0x0100";
142 match "release" "0x0000";
143 action "/usr/local/bin/ezdownload -f /usr/local/share/usb/firmware/0854.0100.0_01.hex $device-name";
146 # Firmware download for Entrega Serial DB25 adapter.
148 match "vendor" "0x1645";
149 match "product" "0x8001";
150 match "release" "0x0101";
151 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";
154 # This entry starts the ColdSync tool in daemon mode. Make sure you have an up
155 # to date /usr/local/etc/palms. We override the 'listen' settings for port and
156 # type in /usr/local/etc/coldsync.conf.
158 match "system" "USB";
159 match "subsystem" "DEVICE";
160 match "type" "ATTACH";
161 match "vendor" "0x082d";
162 match "product" "0x0100";
163 match "release" "0x0100";
164 action "/usr/local/bin/coldsync -md -p /dev/$cdev -t usb";
168 # Rescan scsi device-names on attach, but not detach. However, it is
169 # disabled by default due to reports of problems.
172 device-name "$scsi-controller-regex";
173 // action "camcontrol rescan all";
176 # Don't even try to second guess what to do about drivers that don't
177 # match here. Instead, pass it off to syslog. Commented out for the
178 # moment, as the pnpinfo variable isn't set in devd yet. Individual
179 # variables within the bus supplied pnpinfo are set.
181 # action "logger Unknown device: $pnpinfo $location $bus";
184 # Various logging of unknown devices.
186 match "bus" "uhub[0-9]+";
187 action "logger Unknown USB device: vendor $vendor product $product \
191 # Some PC-CARDs don't offer numerical manufacturer/product IDs, just
192 # show the CIS info there.
194 match "bus" "pccard[0-9]+";
195 match "manufacturer" "0xffffffff";
196 match "product" "0xffffffff";
197 action "logger Unknown PCCARD device: CISproduct $cisproduct \
198 CIS-vendor $cisvendor bus $bus";
202 match "bus" "pccard[0-9]+";
203 action "logger Unknown PCCARD device: manufacturer $manufacturer \
204 product $product CISproduct $cisproduct CIS-vendor \
205 $cisvendor bus $bus";
209 match "bus" "cardbus[0-9]+";
210 action "logger Unknown Cardbus device: device $device class $class \
211 vendor $vendor bus $bus";
214 # Switch power profiles when the AC line state changes.
216 match "system" "ACPI";
217 match "subsystem" "ACAD";
218 action "/etc/rc.d/power_profile $notify";
221 # Notify all users before beginning emergency shutdown when we get
222 # a _CRT or _HOT thermal event and we're going to power down the system
225 match "system" "ACPI";
226 match "subsystem" "Thermal";
227 match "notify" "0xcc";
228 action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'";
231 # Sample ZFS problem reports handling.
233 match "system" "ZFS";
234 match "type" "zpool";
235 action "logger -p kern.err 'ZFS: failed to load zpool $pool'";
239 match "system" "ZFS";
241 action "logger -p kern.err 'ZFS: vdev failure, zpool=$pool type=$type'";
245 match "system" "ZFS";
247 action "logger -p kern.warn 'ZFS: zpool I/O failure, zpool=$pool error=$zio_err'";
251 match "system" "ZFS";
253 action "logger -p kern.warn 'ZFS: vdev I/O failure, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size error=$zio_err'";
257 match "system" "ZFS";
258 match "type" "checksum";
259 action "logger -p kern.warn 'ZFS: checksum mismatch, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size'";
262 # User requested suspend, so perform preparation steps and then execute
263 # the actual suspend process.
265 match "system" "ACPI";
266 match "subsystem" "Suspend";
267 action "/etc/rc.suspend acpi $notify";
270 match "system" "ACPI";
271 match "subsystem" "Resume";
272 action "/etc/rc.resume acpi $notify";
275 /* EXAMPLES TO END OF FILE
277 # An example of something that a vendor might install if you were to
278 # add their device. This might reside in /usr/local/etc/devd/deqna.conf.
279 # A deqna is, in this hypothetical example, a pccard ethernet-like device.
280 # Students of history may know other devices by this name, and will get
281 # the in-jokes in this entry.
283 match "bus" "pccard[0-9]+";
284 match "manufacturer" "0x1234";
285 match "product" "0x2323";
286 action "kldload if_deqna";
289 device-name "deqna[0-9]+";
290 action "/etc/pccard_ether $device-name start";
293 device-name "deqna[0-9]+";
294 action "/etc/pccard_ether $device-name stop";
297 # Examples of notify hooks. A notify is a generic way for a kernel
298 # subsystem to send event notification to userland.
300 # Here are some examples of ACPI notify handlers. ACPI subsystems that
301 # generate notifies include the AC adapter, power/sleep buttons,
302 # control method batteries, lid switch, and thermal zones.
304 # Information returned is not always the same as the ACPI notify
305 # events. See the ACPI specification for more information about
306 # notifies. Here is the information returned for each subsystem:
308 # ACAD: AC line state (0 is offline, 1 is online)
309 # Button: Button pressed (0 for power, 1 for sleep)
310 # CMBAT: ACPI battery events
311 # Lid: Lid state (0 is closed, 1 is open)
312 # RCTL: Resource limits
313 # Suspend, Resume: Suspend and resume notification
314 # Thermal: ACPI thermal zone events
316 # This example calls a script when the AC state changes, passing the
317 # notify value as the first argument. If the state is 0x00, it might
318 # call some sysctls to implement economy mode. If 0x01, it might set
319 # the mode to performance.
321 match "system" "ACPI";
322 match "subsystem" "ACAD";
323 action "/etc/acpi_ac $notify";
326 # This example works around a memory leak in PostgreSQL, restarting
327 # it when the "user:pgsql:swap:devctl=1G" rctl(8) rule gets triggered.
329 match "system" "RCTL";
330 match "rule" "user:70:swap:.*";
331 action "/usr/local/etc/rc.d/postgresql restart";