devd.conf revision 238308
1# $FreeBSD: head/etc/devd.conf 238308 2012-07-09 20:11:32Z hrs $ 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 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"; 18 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)\ 24 [0-9]+"; 25}; 26 27# Note that the attach/detach with the highest value wins, so that one can 28# override these general rules. 29 30# 31# Configure the interface on attach. Due to a historical accident, this 32# script is called pccard_ether. 33# 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 38# 39notify 0 { 40 match "system" "IFNET"; 41 match "subsystem" "!usbus[0-9]+"; 42 match "type" "ATTACH"; 43 action "/etc/pccard_ether $subsystem start"; 44}; 45 46# 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. 51# 52notify 0 { 53 match "system" "IFNET"; 54 match "type" "LINK_UP"; 55 media-type "ethernet"; 56 action "/etc/rc.d/dhclient quietstart $subsystem"; 57}; 58 59# 60# Like Ethernet devices, but separate because 61# they have a different media type. We may want 62# to exploit this later. 63# 64detach 0 { 65 media-type "802.11"; 66 action "/etc/pccard_ether $device-name stop"; 67}; 68attach 0 { 69 media-type "802.11"; 70 action "/etc/pccard_ether $device-name start"; 71}; 72notify 0 { 73 match "system" "IFNET"; 74 match "type" "LINK_UP"; 75 media-type "802.11"; 76 action "/etc/rc.d/dhclient quietstart $subsystem"; 77}; 78 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. 83attach 100 { 84 device-name "ed50"; 85 action "ifconfig $device-name inet 1.2.3.4 netmask 0xffff0000"; 86}; 87detach 100 { 88 device-name "ed50"; 89}; 90 91# When a USB Bluetooth dongle appears, activate it 92attach 100 { 93 device-name "ubt[0-9]+"; 94 action "/etc/rc.d/bluetooth quietstart $device-name"; 95}; 96detach 100 { 97 device-name "ubt[0-9]+"; 98 action "/etc/rc.d/bluetooth quietstop $device-name"; 99}; 100 101# Firmware downloader for Atheros AR3011 based USB Bluetooth devices 102#attach 100 { 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"; 106#}; 107 108# When a USB keyboard arrives, attach it as the console keyboard. 109attach 100 { 110 device-name "ukbd0"; 111 action "/etc/rc.d/syscons setkeyboard /dev/ukbd0"; 112}; 113detach 100 { 114 device-name "ukbd0"; 115 action "/etc/rc.d/syscons setkeyboard /dev/kbd0"; 116}; 117 118attach 100 { 119 device-name "ums[0-9]+"; 120 action "/etc/rc.d/moused quietstart $device-name"; 121}; 122 123detach 100 { 124 device-name "ums[0-9]+"; 125 action "/etc/rc.d/moused stop $device-name"; 126}; 127 128# Firmware download into the ActiveWire board. After the firmware download is 129# done, the device detaches and reappears as something new and shiny 130# automatically. 131attach 100 { 132 match "vendor" "0x0854"; 133 match "product" "0x0100"; 134 match "release" "0x0000"; 135 action "/usr/local/bin/ezdownload -f /usr/local/share/usb/firmware/0854.0100.0_01.hex $device-name"; 136}; 137 138# Firmware download for Entrega Serial DB25 adapter. 139attach 100 { 140 match "vendor" "0x1645"; 141 match "product" "0x8001"; 142 match "release" "0x0101"; 143 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"; 144}; 145 146# This entry starts the ColdSync tool in daemon mode. Make sure you have an up 147# to date /usr/local/etc/palms. We override the 'listen' settings for port and 148# type in /usr/local/etc/coldsync.conf. 149notify 100 { 150 match "system" "USB"; 151 match "subsystem" "DEVICE"; 152 match "type" "ATTACH"; 153 match "vendor" "0x082d"; 154 match "product" "0x0100"; 155 match "release" "0x0100"; 156 action "/usr/local/bin/coldsync -md -p /dev/$cdev -t usb"; 157}; 158 159# 160# Rescan scsi device-names on attach, but not detach. However, it is 161# disabled by default due to reports of problems. 162# 163attach 0 { 164 device-name "$scsi-controller-regex"; 165// action "camcontrol rescan all"; 166}; 167 168# Don't even try to second guess what to do about drivers that don't 169# match here. Instead, pass it off to syslog. Commented out for the 170# moment, as the pnpinfo variable isn't set in devd yet. Individual 171# variables within the bus supplied pnpinfo are set. 172nomatch 0 { 173# action "logger Unknown device: $pnpinfo $location $bus"; 174}; 175 176# Various logging of unknown devices. 177nomatch 10 { 178 match "bus" "uhub[0-9]+"; 179 action "logger Unknown USB device: vendor $vendor product $product \ 180 bus $bus"; 181}; 182 183# Some PC-CARDs don't offer numerical manufacturer/product IDs, just 184# show the CIS info there. 185nomatch 20 { 186 match "bus" "pccard[0-9]+"; 187 match "manufacturer" "0xffffffff"; 188 match "product" "0xffffffff"; 189 action "logger Unknown PCCARD device: CISproduct $cisproduct \ 190 CIS-vendor $cisvendor bus $bus"; 191}; 192 193nomatch 10 { 194 match "bus" "pccard[0-9]+"; 195 action "logger Unknown PCCARD device: manufacturer $manufacturer \ 196 product $product CISproduct $cisproduct CIS-vendor \ 197 $cisvendor bus $bus"; 198}; 199 200nomatch 10 { 201 match "bus" "cardbus[0-9]+"; 202 action "logger Unknown Cardbus device: device $device class $class \ 203 vendor $vendor bus $bus"; 204}; 205 206# Switch power profiles when the AC line state changes. 207notify 10 { 208 match "system" "ACPI"; 209 match "subsystem" "ACAD"; 210 action "/etc/rc.d/power_profile $notify"; 211}; 212 213# Notify all users before beginning emergency shutdown when we get 214# a _CRT or _HOT thermal event and we're going to power down the system 215# very soon. 216notify 10 { 217 match "system" "ACPI"; 218 match "subsystem" "Thermal"; 219 match "notify" "0xcc"; 220 action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'"; 221}; 222 223# Sample ZFS problem reports handling. 224notify 10 { 225 match "system" "ZFS"; 226 match "type" "zpool"; 227 action "logger -p kern.err 'ZFS: failed to load zpool $pool'"; 228}; 229 230notify 10 { 231 match "system" "ZFS"; 232 match "type" "vdev"; 233 action "logger -p kern.err 'ZFS: vdev failure, zpool=$pool type=$type'"; 234}; 235 236notify 10 { 237 match "system" "ZFS"; 238 match "type" "data"; 239 action "logger -p kern.warn 'ZFS: zpool I/O failure, zpool=$pool error=$zio_err'"; 240}; 241 242notify 10 { 243 match "system" "ZFS"; 244 match "type" "io"; 245 action "logger -p kern.warn 'ZFS: vdev I/O failure, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size error=$zio_err'"; 246}; 247 248notify 10 { 249 match "system" "ZFS"; 250 match "type" "checksum"; 251 action "logger -p kern.warn 'ZFS: checksum mismatch, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size'"; 252}; 253 254# User requested suspend, so perform preparation steps and then execute 255# the actual suspend process. 256notify 10 { 257 match "system" "ACPI"; 258 match "subsystem" "Suspend"; 259 action "/etc/rc.suspend acpi $notify"; 260}; 261notify 10 { 262 match "system" "ACPI"; 263 match "subsystem" "Resume"; 264 action "/etc/rc.resume acpi $notify"; 265}; 266 267/* EXAMPLES TO END OF FILE 268 269# An example of something that a vendor might install if you were to 270# add their device. This might reside in /usr/local/etc/devd/deqna.conf. 271# A deqna is, in this hypothetical example, a pccard ethernet-like device. 272# Students of history may know other devices by this name, and will get 273# the in-jokes in this entry. 274nomatch 10 { 275 match "bus" "pccard[0-9]+"; 276 match "manufacturer" "0x1234"; 277 match "product" "0x2323"; 278 action "kldload if_deqna"; 279}; 280attach 10 { 281 device-name "deqna[0-9]+"; 282 action "/etc/pccard_ether $device-name start"; 283}; 284detach 10 { 285 device-name "deqna[0-9]+"; 286 action "/etc/pccard_ether $device-name stop"; 287}; 288 289# Examples of notify hooks. A notify is a generic way for a kernel 290# subsystem to send event notification to userland. 291 292# Here are some examples of ACPI notify handlers. ACPI subsystems that 293# generate notifies include the AC adapter, power/sleep buttons, 294# control method batteries, lid switch, and thermal zones. 295# 296# Information returned is not always the same as the ACPI notify 297# events. See the ACPI specification for more information about 298# notifies. Here is the information returned for each subsystem: 299# 300# ACAD: AC line state (0 is offline, 1 is online) 301# Button: Button pressed (0 for power, 1 for sleep) 302# CMBAT: ACPI battery events 303# Lid: Lid state (0 is closed, 1 is open) 304# RCTL: Resource limits 305# Suspend, Resume: Suspend and resume notification 306# Thermal: ACPI thermal zone events 307# 308# This example calls a script when the AC state changes, passing the 309# notify value as the first argument. If the state is 0x00, it might 310# call some sysctls to implement economy mode. If 0x01, it might set 311# the mode to performance. 312notify 10 { 313 match "system" "ACPI"; 314 match "subsystem" "ACAD"; 315 action "/etc/acpi_ac $notify"; 316}; 317 318# This example works around a memory leak in PostgreSQL, restarting 319# it when the "user:pgsql:swap:devctl=1G" rctl(8) rule gets triggered. 320notify 0 { 321 match "system" "RCTL"; 322 match "rule" "user:70:swap:.*"; 323 action "/usr/local/etc/rc.d/postgresql restart"; 324}; 325 326*/ 327