devd.conf revision 168497
1# $FreeBSD: head/etc/devd.conf 168497 2007-04-08 16:05:23Z pjd $ 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 #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# 34notify 0 { 35 match "system" "IFNET"; 36 match "type" "ATTACH"; 37 action "/etc/pccard_ether $subsystem start"; 38}; 39 40notify 0 { 41 match "system" "IFNET"; 42 match "type" "DETACH"; 43 action "/etc/pccard_ether $subsystem stop"; 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 automaticly 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 start $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 start $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 start $device-name"; 95}; 96detach 100 { 97 device-name "ubt[0-9]+"; 98 action "/etc/rc.d/bluetooth stop $device-name"; 99}; 100 101# When a USB keyboard arrives, attach it as the console keyboard. 102attach 100 { 103 device-name "ukbd0"; 104 action "/etc/rc.d/syscons setkeyboard /dev/ukbd0"; 105}; 106detach 100 { 107 device-name "ukbd0"; 108 action "/etc/rc.d/syscons setkeyboard /dev/kbd0"; 109}; 110 111# The entry below starts moused when a mouse is plugged in. Moused 112# stops automatically (actually it bombs :) when the device disappears. 113attach 100 { 114 device-name "ums[0-9]+"; 115 action "/etc/rc.d/moused start $device-name"; 116}; 117 118# Firmware download into the ActiveWire board. After the firmware download is 119# done the device detaches and reappears as something new and shiny 120# automatically. 121attach 100 { 122 match "vendor" "0x0854"; 123 match "product" "0x0100"; 124 match "release" "0x0000"; 125 action "/usr/local/bin/ezdownload -f /usr/local/share/usb/firmware/0854.0100.0_01.hex $device-name"; 126}; 127 128# Firmware download for Entrega Serial DB25 adapter. 129attach 100 { 130 match "vendor" "0x1645"; 131 match "product" "0x8001"; 132 match "release" "0x0101"; 133 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"; 134}; 135 136# This entry starts the ColdSync tool in daemon mode. Make sure you have an up 137# to date /usr/local/etc/palms. We override the 'listen' settings for port and 138# type in /usr/local/etc/coldsync.conf. 139attach 100 { 140 device-name "ugen[0-9]+"; 141 match "vendor" "0x082d"; 142 match "product" "0x0100"; 143 match "release" "0x0100"; 144 action "/usr/local/bin/coldsync -md -p /dev/$device-name -t usb"; 145}; 146 147# 148# Rescan scsi device-names on attach, but not detach. However, it is 149# disabled by default due to reports of problems. 150# 151attach 0 { 152 device-name "$scsi-controller-regex"; 153// action "camcontrol rescan all"; 154}; 155 156# Don't even try to second guess what to do about drivers that don't 157# match here. Instead, pass it off to syslog. Commented out for the 158# moment, as the pnpinfo variable isn't set in devd yet. Individual 159# variables within the bus supplied pnpinfo are set. 160nomatch 0 { 161# action "logger Unknown device: $pnpinfo $location $bus"; 162}; 163 164# Various logging of unknown devices. 165nomatch 10 { 166 match "bus" "uhub[0-9]+"; 167 action "logger Unknown USB device: vendor $vendor product $product \ 168 bus $bus"; 169}; 170 171# Some PC-CARDs don't offer numerical manufacturer/product IDs, just 172# show the CIS info there. 173nomatch 20 { 174 match "bus" "pccard[0-9]+"; 175 match "manufacturer" "0xffffffff"; 176 match "product" "0xffffffff"; 177 action "logger Unknown PCCARD device: CISproduct $cisproduct \ 178 CIS-vendor $cisvendor bus $bus"; 179}; 180 181nomatch 10 { 182 match "bus" "pccard[0-9]+"; 183 action "logger Unknown PCCARD device: manufacturer $manufacturer \ 184 product $product CISproduct $cisproduct CIS-vendor \ 185 $cisvendor bus $bus"; 186}; 187 188nomatch 10 { 189 match "bus" "cardbus[0-9]+"; 190 action "logger Unknown Cardbus device: device $device class $class \ 191 vendor $vendor bus $bus"; 192}; 193 194# Switch power profiles when the AC line state changes. 195notify 10 { 196 match "system" "ACPI"; 197 match "subsystem" "ACAD"; 198 action "/etc/rc.d/power_profile $notify"; 199}; 200 201# Notify all users before beginning emergency shutdown when we get 202# a _CRT or _HOT thermal event and we're going to power down the system 203# very soon. 204notify 10 { 205 match "system" "ACPI"; 206 match "subsystem" "Thermal"; 207 match "notify" "0xcc"; 208 action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'"; 209}; 210 211# Sample ZFS problem reports handling. 212notify 10 { 213 match "system" "ZFS"; 214 match "type" "zpool"; 215 action "logger -p kern.err 'ZFS: failed to load zpool $pool'"; 216}; 217 218notify 10 { 219 match "system" "ZFS"; 220 match "type" "vdev"; 221 action "logger -p kern.err 'ZFS: vdev failure, zpool=$pool type=$type'"; 222}; 223 224notify 10 { 225 match "system" "ZFS"; 226 match "type" "data"; 227 action "logger -p kern.warn 'ZFS: zpool I/O failure, zpool=$pool error=$zio_err'"; 228}; 229 230notify 10 { 231 match "system" "ZFS"; 232 match "type" "io"; 233 action "logger -p kern.warn 'ZFS: vdev I/O failure, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size error=$zio_err'"; 234}; 235 236notify 10 { 237 match "system" "ZFS"; 238 match "type" "checksum"; 239 action "logger -p kern.warn 'ZFS: checksum mismatch, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size'"; 240}; 241 242/* EXAMPLES TO END OF FILE 243 244# The following might be an example of something that a vendor might 245# install if you were to add their device. This might reside in 246# /usr/local/etc/devd/deqna.conf. A deqna is, in this hypothetical 247# example, a pccard ethernet-like device. Students of history may 248# know other devices by this name, and will get the in-jokes in this 249# entry. 250nomatch 10 { 251 match "bus" "pccard[0-9]+"; 252 match "manufacturer" "0x1234"; 253 match "product" "0x2323"; 254 action "kldload if_deqna"; 255}; 256attach 10 { 257 device-name "deqna[0-9]+"; 258 action "/etc/pccard_ether $device-name start"; 259}; 260detach 10 { 261 device-name "deqna[0-9]+"; 262 action "/etc/pccard_ether $device-name stop"; 263}; 264 265# Examples of notify hooks. A notify is a generic way for a kernel 266# subsystem to send event notification to userland. 267# 268# Here are some examples of ACPI notify handlers. ACPI subsystems that 269# generate notifies include the AC adapter, power/sleep buttons, 270# control method batteries, lid switch, and thermal zones. 271# 272# Information returned is not always the same as the ACPI notify 273# events. See the ACPI specification for more information about 274# notifies. Here is the information returned for each subsystem: 275# 276# ACAD: AC line state (0 is offline, 1 is online) 277# Button: Button pressed (0 for power, 1 for sleep) 278# CMBAT: ACPI battery events 279# Lid: Lid state (0 is closed, 1 is open) 280# Thermal: ACPI thermal zone events 281# 282# This example calls a script when the AC state changes, passing the 283# notify value as the first argument. If the state is 0x00, it might 284# call some sysctls to implement economy mode. If 0x01, it might set 285# the mode to performance. 286notify 10 { 287 match "system" "ACPI"; 288 match "subsystem" "ACAD"; 289 action "/etc/acpi_ac $notify"; 290}; 291*/ 292