devd.conf revision 241084
1169Sohair# $FreeBSD: stable/9/etc/devd.conf 241084 2012-10-01 05:48:46Z hselasky $ 22362Sohair# 30Sduke# Refer to devd.conf(5) and devd(8) man pages for the details on how to 40Sduke# run and configure devd. 50Sduke# 60Sduke 70Sduke# NB: All regular expressions have an implicit ^$ around them. 80Sduke# NB: device-name is shorthand for 'match device-name' 90Sduke 100Sdukeoptions { 110Sduke # Each "directory" directive adds a directory to the list of 120Sduke # directories that we scan for files. Files are loaded in the order 130Sduke # that they are returned from readdir(3). The rule-sets are combined 140Sduke # to create a DFA that's used to match events to actions. 150Sduke directory "/etc/devd"; 160Sduke directory "/usr/local/etc/devd"; 170Sduke pid-file "/var/run/devd.pid"; 180Sduke 192362Sohair # Setup some shorthand for regex that we use later in the file. 202362Sohair #XXX Yes, these are gross -- imp 212362Sohair set scsi-controller-regex 220Sduke "(aac|adv|adw|aha|ahb|ahc|ahd|aic|amd|amr|asr|bt|ciss|ct|dpt|\ 230Sduke esp|ida|iir|ips|isp|mlx|mly|mpt|ncr|ncv|nsp|stg|sym|trm|wds)\ 240Sduke [0-9]+"; 250Sduke}; 260Sduke 270Sduke# Note that the attach/detach with the highest value wins, so that one can 280Sduke# override these general rules. 290Sduke 300Sduke# 310Sduke# Configure the interface on attach. Due to a historical accident, this 320Sduke# script is called pccard_ether. 330Sduke# 340Sduke# NB: DETACH events are ignored; the kernel should handle all cleanup 350Sduke# (routes, arp cache). Beware of races against immediate create 360Sduke# of a device with the same name; e.g. 370Sduke# ifconfig bridge0 destroy; ifconfig bridge0 create 380Sduke# 390Sdukenotify 0 { 400Sduke match "system" "IFNET"; 410Sduke match "type" "ATTACH"; 420Sduke action "/etc/pccard_ether $subsystem start"; 430Sduke}; 44169Sohair 450Sduke# 460Sduke# Try to start dhclient on Ethernet-like interfaces when the link comes 470Sduke# up. Only devices that are configured to support DHCP will actually 480Sduke# run it. No link down rule exists because dhclient automatically exits 490Sduke# when the link goes down. 500Sduke# 510Sdukenotify 0 { 520Sduke match "system" "IFNET"; 530Sduke match "type" "LINK_UP"; 540Sduke media-type "ethernet"; 55169Sohair action "/etc/rc.d/dhclient quietstart $subsystem"; 560Sduke}; 570Sduke 580Sduke# 59169Sohair# Like Ethernet devices, but separate because 60169Sohair# they have a different media type. We may want 610Sduke# to exploit this later. 62169Sohair# 63169Sohairdetach 0 { 64169Sohair media-type "802.11"; 650Sduke action "/etc/pccard_ether $device-name stop"; 66169Sohair}; 670Sdukeattach 0 { 68169Sohair media-type "802.11"; 69169Sohair action "/etc/pccard_ether $device-name start"; 70169Sohair}; 710Sdukenotify 0 { 72169Sohair match "system" "IFNET"; 730Sduke match "type" "LINK_UP"; 740Sduke media-type "802.11"; 750Sduke action "/etc/rc.d/dhclient quietstart $subsystem"; 760Sduke}; 770Sduke 78169Sohair# An entry like this might be in a different file, but is included here 79169Sohair# as an example of how to override things. Normally 'ed50' would match 80169Sohair# the above attach/detach stuff, but the value of 100 makes it 81169Sohair# hard wired to 1.2.3.4. 82169Sohairattach 100 { 830Sduke device-name "ed50"; 84169Sohair action "ifconfig $device-name inet 1.2.3.4 netmask 0xffff0000"; 85169Sohair}; 86169Sohairdetach 100 { 87169Sohair device-name "ed50"; 88169Sohair}; 89169Sohair 90169Sohair# When a USB Bluetooth dongle appears, activate it 910Sdukeattach 100 { 920Sduke device-name "ubt[0-9]+"; 93 action "/etc/rc.d/bluetooth quietstart $device-name"; 94}; 95detach 100 { 96 device-name "ubt[0-9]+"; 97 action "/etc/rc.d/bluetooth quietstop $device-name"; 98}; 99 100# Firmware downloader for Atheros AR3011 based USB Bluetooth devices 101#attach 100 { 102# match "vendor" "0x0cf3"; 103# match "product" "0x3000"; 104# action "sleep 2 && /usr/sbin/ath3kfw -d $device-name -f /usr/local/etc/ath3k-1.fw"; 105#}; 106 107# When a USB keyboard arrives, attach it as the console keyboard. 108attach 100 { 109 device-name "ukbd0"; 110 action "/etc/rc.d/syscons setkeyboard /dev/ukbd0"; 111}; 112detach 100 { 113 device-name "ukbd0"; 114 action "/etc/rc.d/syscons setkeyboard /dev/kbd0"; 115}; 116 117notify 100 { 118 match "system" "DEVFS"; 119 match "subsystem" "CDEV"; 120 match "type" "CREATE"; 121 match "cdev" "ums[0-9]+"; 122 123 action "/etc/rc.d/moused quietstart $cdev"; 124}; 125 126notify 100 { 127 match "system" "DEVFS"; 128 match "subsystem" "CDEV"; 129 match "type" "DESTROY"; 130 match "cdev" "ums[0-9]+"; 131 132 action "/etc/rc.d/moused stop $cdev"; 133}; 134 135# Firmware download into the ActiveWire board. After the firmware download is 136# done, the device detaches and reappears as something new and shiny 137# automatically. 138attach 100 { 139 match "vendor" "0x0854"; 140 match "product" "0x0100"; 141 match "release" "0x0000"; 142 action "/usr/local/bin/ezdownload -f /usr/local/share/usb/firmware/0854.0100.0_01.hex $device-name"; 143}; 144 145# Firmware download for Entrega Serial DB25 adapter. 146attach 100 { 147 match "vendor" "0x1645"; 148 match "product" "0x8001"; 149 match "release" "0x0101"; 150 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"; 151}; 152 153# This entry starts the ColdSync tool in daemon mode. Make sure you have an up 154# to date /usr/local/etc/palms. We override the 'listen' settings for port and 155# type in /usr/local/etc/coldsync.conf. 156notify 100 { 157 match "system" "USB"; 158 match "subsystem" "DEVICE"; 159 match "type" "ATTACH"; 160 match "vendor" "0x082d"; 161 match "product" "0x0100"; 162 match "release" "0x0100"; 163 action "/usr/local/bin/coldsync -md -p /dev/$cdev -t usb"; 164}; 165 166# 167# Rescan scsi device-names on attach, but not detach. However, it is 168# disabled by default due to reports of problems. 169# 170attach 0 { 171 device-name "$scsi-controller-regex"; 172// action "camcontrol rescan all"; 173}; 174 175# Don't even try to second guess what to do about drivers that don't 176# match here. Instead, pass it off to syslog. Commented out for the 177# moment, as the pnpinfo variable isn't set in devd yet. Individual 178# variables within the bus supplied pnpinfo are set. 179nomatch 0 { 180# action "logger Unknown device: $pnpinfo $location $bus"; 181}; 182 183# Various logging of unknown devices. 184nomatch 10 { 185 match "bus" "uhub[0-9]+"; 186 action "logger Unknown USB device: vendor $vendor product $product \ 187 bus $bus"; 188}; 189 190# Some PC-CARDs don't offer numerical manufacturer/product IDs, just 191# show the CIS info there. 192nomatch 20 { 193 match "bus" "pccard[0-9]+"; 194 match "manufacturer" "0xffffffff"; 195 match "product" "0xffffffff"; 196 action "logger Unknown PCCARD device: CISproduct $cisproduct \ 197 CIS-vendor $cisvendor bus $bus"; 198}; 199 200nomatch 10 { 201 match "bus" "pccard[0-9]+"; 202 action "logger Unknown PCCARD device: manufacturer $manufacturer \ 203 product $product CISproduct $cisproduct CIS-vendor \ 204 $cisvendor bus $bus"; 205}; 206 207nomatch 10 { 208 match "bus" "cardbus[0-9]+"; 209 action "logger Unknown Cardbus device: device $device class $class \ 210 vendor $vendor bus $bus"; 211}; 212 213# Switch power profiles when the AC line state changes. 214notify 10 { 215 match "system" "ACPI"; 216 match "subsystem" "ACAD"; 217 action "/etc/rc.d/power_profile $notify"; 218}; 219 220# Notify all users before beginning emergency shutdown when we get 221# a _CRT or _HOT thermal event and we're going to power down the system 222# very soon. 223notify 10 { 224 match "system" "ACPI"; 225 match "subsystem" "Thermal"; 226 match "notify" "0xcc"; 227 action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'"; 228}; 229 230# Sample ZFS problem reports handling. 231notify 10 { 232 match "system" "ZFS"; 233 match "type" "zpool"; 234 action "logger -p kern.err 'ZFS: failed to load zpool $pool'"; 235}; 236 237notify 10 { 238 match "system" "ZFS"; 239 match "type" "vdev"; 240 action "logger -p kern.err 'ZFS: vdev failure, zpool=$pool type=$type'"; 241}; 242 243notify 10 { 244 match "system" "ZFS"; 245 match "type" "data"; 246 action "logger -p kern.warn 'ZFS: zpool I/O failure, zpool=$pool error=$zio_err'"; 247}; 248 249notify 10 { 250 match "system" "ZFS"; 251 match "type" "io"; 252 action "logger -p kern.warn 'ZFS: vdev I/O failure, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size error=$zio_err'"; 253}; 254 255notify 10 { 256 match "system" "ZFS"; 257 match "type" "checksum"; 258 action "logger -p kern.warn 'ZFS: checksum mismatch, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size'"; 259}; 260 261# User requested suspend, so perform preparation steps and then execute 262# the actual suspend process. 263notify 10 { 264 match "system" "ACPI"; 265 match "subsystem" "Suspend"; 266 action "/etc/rc.suspend acpi $notify"; 267}; 268notify 10 { 269 match "system" "ACPI"; 270 match "subsystem" "Resume"; 271 action "/etc/rc.resume acpi $notify"; 272}; 273 274/* EXAMPLES TO END OF FILE 275 276# An example of something that a vendor might install if you were to 277# add their device. This might reside in /usr/local/etc/devd/deqna.conf. 278# A deqna is, in this hypothetical example, a pccard ethernet-like device. 279# Students of history may know other devices by this name, and will get 280# the in-jokes in this entry. 281nomatch 10 { 282 match "bus" "pccard[0-9]+"; 283 match "manufacturer" "0x1234"; 284 match "product" "0x2323"; 285 action "kldload if_deqna"; 286}; 287attach 10 { 288 device-name "deqna[0-9]+"; 289 action "/etc/pccard_ether $device-name start"; 290}; 291detach 10 { 292 device-name "deqna[0-9]+"; 293 action "/etc/pccard_ether $device-name stop"; 294}; 295 296# Examples of notify hooks. A notify is a generic way for a kernel 297# subsystem to send event notification to userland. 298 299# Here are some examples of ACPI notify handlers. ACPI subsystems that 300# generate notifies include the AC adapter, power/sleep buttons, 301# control method batteries, lid switch, and thermal zones. 302# 303# Information returned is not always the same as the ACPI notify 304# events. See the ACPI specification for more information about 305# notifies. Here is the information returned for each subsystem: 306# 307# ACAD: AC line state (0 is offline, 1 is online) 308# Button: Button pressed (0 for power, 1 for sleep) 309# CMBAT: ACPI battery events 310# Lid: Lid state (0 is closed, 1 is open) 311# RCTL: Resource limits 312# Suspend, Resume: Suspend and resume notification 313# Thermal: ACPI thermal zone events 314# 315# This example calls a script when the AC state changes, passing the 316# notify value as the first argument. If the state is 0x00, it might 317# call some sysctls to implement economy mode. If 0x01, it might set 318# the mode to performance. 319notify 10 { 320 match "system" "ACPI"; 321 match "subsystem" "ACAD"; 322 action "/etc/acpi_ac $notify"; 323}; 324 325# This example works around a memory leak in PostgreSQL, restarting 326# it when the "user:pgsql:swap:devctl=1G" rctl(8) rule gets triggered. 327notify 0 { 328 match "system" "RCTL"; 329 match "rule" "user:70:swap:.*"; 330 action "/usr/local/etc/rc.d/postgresql restart" 331}; 332 333*/ 334