1# $FreeBSD$ 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|aacraid|ahc|ahd|amr|ciss|\ 23 esp|ida|iir|ips|isp|mlx|mly|mpr|mps|mpt|sym|trm)\ 24 [0-9]+"; 25 set wifi-driver-regex 26 "(ath|bwi|bwn|ipw|iwi|iwm|iwn|malo|mwl|otus|ral|rsu|rtwn|rum|\ 27 run|uath|upgt|ural|urtw|wi|wpi|wtap|zyd)[0-9]+"; 28}; 29 30# Note that the attach/detach with the highest value wins, so that one can 31# override these general rules. 32 33# 34# Configure the interface on attach. Due to a historical accident, this 35# script is called pccard_ether. We omit the usbus devices because those 36# devices are associated with the USB Bus and provide an ifnet device to 37# allow usb traffic to be captured with usbdump(8). 38# 39# NB: DETACH events are ignored; the kernel should handle all cleanup 40# (routes, arp cache). Beware of races against immediate create 41# of a device with the same name; e.g. 42# ifconfig bridge0 destroy; ifconfig bridge0 create 43# 44notify 0 { 45 match "system" "IFNET"; 46 match "subsystem" "!(usbus|wlan)[0-9]+"; 47 match "type" "ATTACH"; 48 action "/etc/pccard_ether $subsystem start"; 49}; 50 51# 52# Try to start dhclient on Ethernet-like interfaces when the link comes 53# up. Only devices that are configured to support DHCP will actually 54# run it. No link down rule exists because dhclient automatically exits 55# when the link goes down. 56# 57notify 0 { 58 match "system" "IFNET"; 59 match "type" "LINK_UP"; 60 media-type "ethernet"; 61 action "service dhclient quietstart $subsystem"; 62}; 63 64# 65# Like Ethernet devices, but separate because 802.11 require spawning 66# wlan(4) interface. 67# 68attach 0 { 69 device-name "$wifi-driver-regex"; 70 action "/etc/pccard_ether $device-name startchildren"; 71}; 72detach 0 { 73 device-name "$wifi-driver-regex"; 74 action "/etc/pccard_ether $device-name stopchildren"; 75}; 76notify 0 { 77 match "system" "IFNET"; 78 match "type" "LINK_UP"; 79 media-type "802.11"; 80 action "service dhclient quietstart $subsystem"; 81}; 82 83# An entry like this might be in a different file, but is included here 84# as an example of how to override things. Normally 'ed50' would match 85# the above attach/detach stuff, but the value of 100 makes it 86# hard wired to 1.2.3.4. 87attach 100 { 88 device-name "ed50"; 89 action "ifconfig $device-name inet 1.2.3.4 netmask 0xffff0000"; 90}; 91detach 100 { 92 device-name "ed50"; 93}; 94 95# When a USB Bluetooth dongle appears, activate it 96attach 100 { 97 device-name "ubt[0-9]+"; 98 action "service bluetooth quietstart $device-name"; 99}; 100detach 100 { 101 device-name "ubt[0-9]+"; 102 action "service bluetooth quietstop $device-name"; 103}; 104 105# Firmware downloader for Atheros AR3011 based USB Bluetooth devices 106#attach 100 { 107# match "vendor" "0x0cf3"; 108# match "product" "0x3000"; 109# action "sleep 2 && /usr/sbin/ath3kfw -d $device-name -f /usr/local/etc/ath3k-1.fw"; 110#}; 111 112# When a USB keyboard arrives, attach it as the console keyboard. 113attach 100 { 114 device-name "ukbd0"; 115 action "service syscons setkeyboard /dev/ukbd0"; 116}; 117detach 100 { 118 device-name "ukbd0"; 119 action "service syscons setkeyboard /dev/kbd0"; 120}; 121 122notify 100 { 123 match "system" "DEVFS"; 124 match "subsystem" "CDEV"; 125 match "type" "CREATE"; 126 match "cdev" "atp[0-9]+"; 127 128 action "service moused quietstart $cdev"; 129}; 130 131notify 100 { 132 match "system" "DEVFS"; 133 match "subsystem" "CDEV"; 134 match "type" "CREATE"; 135 match "cdev" "ums[0-9]+"; 136 137 action "service moused quietstart $cdev"; 138}; 139 140notify 100 { 141 match "system" "DEVFS"; 142 match "subsystem" "CDEV"; 143 match "type" "CREATE"; 144 match "cdev" "wsp[0-9]+"; 145 146 action "service moused quietstart $cdev"; 147}; 148 149notify 100 { 150 match "system" "DEVFS"; 151 match "subsystem" "CDEV"; 152 match "type" "DESTROY"; 153 match "cdev" "ums[0-9]+"; 154 155 action "service moused stop $cdev"; 156}; 157 158# 159# Rescan SCSI device-names on attach, but not detach. However, it is 160# disabled by default due to reports of problems. 161# 162attach 0 { 163 device-name "$scsi-controller-regex"; 164// action "camcontrol rescan all"; 165}; 166 167# Don't even try to second guess what to do about drivers that don't 168# match here. Instead, pass it off to syslog. Commented out for the 169# moment, as the pnpinfo variable isn't set in devd yet. Individual 170# variables within the bus supplied pnpinfo are set. 171nomatch 0 { 172# action "logger Unknown device: $pnpinfo $location $bus"; 173}; 174 175# Various logging of unknown devices. 176nomatch 10 { 177 match "bus" "uhub[0-9]+"; 178 action "logger Unknown USB device: vendor $vendor product $product \ 179 bus $bus"; 180}; 181 182# Some PC-CARDs don't offer numerical manufacturer/product IDs, just 183# show the CIS info there. 184nomatch 20 { 185 match "bus" "pccard[0-9]+"; 186 match "manufacturer" "0xffffffff"; 187 match "product" "0xffffffff"; 188 action "logger Unknown PCCARD device: CISproduct $cisproduct \ 189 CIS-vendor $cisvendor bus $bus"; 190}; 191 192nomatch 10 { 193 match "bus" "pccard[0-9]+"; 194 action "logger Unknown PCCARD device: manufacturer $manufacturer \ 195 product $product CISproduct $cisproduct CIS-vendor \ 196 $cisvendor bus $bus"; 197}; 198 199nomatch 10 { 200 match "bus" "cardbus[0-9]+"; 201 action "logger Unknown Cardbus device: device $device class $class \ 202 vendor $vendor bus $bus"; 203}; 204 205# Switch power profiles when the AC line state changes. 206notify 10 { 207 match "system" "ACPI"; 208 match "subsystem" "ACAD"; 209 action "service power_profile $notify"; 210}; 211 212# Notify all users before beginning emergency shutdown when we get 213# a _CRT or _HOT thermal event and we're going to power down the system 214# very soon. 215notify 10 { 216 match "system" "ACPI"; 217 match "subsystem" "Thermal"; 218 match "notify" "0xcc"; 219 action "logger -p kern.emerg WARNING: system temperature too high, shutting down soon!"; 220}; 221 222# User requested suspend, so perform preparation steps and then execute 223# the actual suspend process. 224notify 10 { 225 match "system" "ACPI"; 226 match "subsystem" "Suspend"; 227 action "/etc/rc.suspend acpi $notify"; 228}; 229notify 10 { 230 match "system" "ACPI"; 231 match "subsystem" "Resume"; 232 action "/etc/rc.resume acpi $notify"; 233}; 234 235/* EXAMPLES TO END OF FILE 236 237# An example of something that a vendor might install if you were to 238# add their device. This might reside in /usr/local/etc/devd/deqna.conf. 239# A deqna is, in this hypothetical example, a pccard ethernet-like device. 240# Students of history may know other devices by this name, and will get 241# the in-jokes in this entry. 242nomatch 10 { 243 match "bus" "pccard[0-9]+"; 244 match "manufacturer" "0x1234"; 245 match "product" "0x2323"; 246 action "kldload -n if_deqna"; 247}; 248attach 10 { 249 device-name "deqna[0-9]+"; 250 action "/etc/pccard_ether $device-name start"; 251}; 252detach 10 { 253 device-name "deqna[0-9]+"; 254 action "/etc/pccard_ether $device-name stop"; 255}; 256 257# Examples of notify hooks. A notify is a generic way for a kernel 258# subsystem to send event notification to userland. 259 260# Here are some examples of ACPI notify handlers. ACPI subsystems that 261# generate notifies include the AC adapter, power/sleep buttons, 262# control method batteries, lid switch, and thermal zones. 263# 264# Information returned is not always the same as the ACPI notify 265# events. See the ACPI specification for more information about 266# notifies. Here is the information returned for each subsystem: 267# 268# ACAD: AC line state (0 is offline, 1 is online) 269# Button: Button pressed (0 for power, 1 for sleep) 270# CMBAT: ACPI battery events 271# Lid: Lid state (0 is closed, 1 is open) 272# Suspend, Resume: Suspend and resume notification 273# Thermal: ACPI thermal zone events 274# 275# This example calls a script when the AC state changes, passing the 276# notify value as the first argument. If the state is 0x00, it might 277# call some sysctls to implement economy mode. If 0x01, it might set 278# the mode to performance. 279notify 10 { 280 match "system" "ACPI"; 281 match "subsystem" "ACAD"; 282 action "/etc/acpi_ac $notify"; 283}; 284 285# This example works around a memory leak in PostgreSQL, restarting 286# it when the "user:postgres:swap:devctl=1G" rctl(8) rule gets triggered. 287notify 0 { 288 match "system" "RCTL"; 289 match "rule" "user:770:swap:.*"; 290 action "service postgresql restart"; 291}; 292 293# Discard autofs caches, useful for the -media special map. 294notify 100 { 295 match "system" "GEOM"; 296 match "subsystem" "DEV"; 297 action "/usr/sbin/automount -c"; 298}; 299 300# Handle userland coredumps. 301# This commented out handler makes it possible to run an 302# automated debugging session after the core dump is generated. 303# Replace action with a proper coredump handler, but be aware that 304# it will run with elevated privileges. 305notify 10 { 306 match "system" "kernel"; 307 match "subsystem" "signal"; 308 match "type" "coredump"; 309 action "logger $comm $core"; 310}; 311 312# Let the init(8) know there's a new USB serial interface it might 313# want to run getty(8) for. This includes device-side tty created 314# by usb_template(4). 315notify 100 { 316 match "system" "DEVFS"; 317 match "subsystem" "CDEV"; 318 match "type" "CREATE"; 319 match "cdev" "ttyU[0-9]+"; 320 action "/sbin/init q"; 321}; 322 323*/ 324