devd.conf revision 207020
1108983Simp# $FreeBSD: head/etc/devd.conf 207020 2010-04-21 21:51:14Z thompsa $ 2108983Simp# 3108983Simp# Refer to devd.conf(5) and devd(8) man pages for the details on how to 4108983Simp# run and configure devd. 5108983Simp# 6108983Simp 7108983Simp# NB: All regular expressions have an implicit ^$ around them. 8108983Simp# NB: device-name is shorthand for 'match device-name' 9108983Simp 10108983Simpoptions { 11108983Simp # Each directory directive adds a directory the list of directories 12108983Simp # that we scan for files. Files are read-in in the order that they 13108983Simp # are returned from readdir(3). The rule-sets are combined to 14108983Simp # create a DFA that's used to match events to actions. 15108983Simp directory "/etc/devd"; 16108983Simp directory "/usr/local/etc/devd"; 17108983Simp pid-file "/var/run/devd.pid"; 18108983Simp 19108983Simp # Setup some shorthand for regex that we use later in the file. 20148471Simp #XXX Yes, these are gross -- imp 21108983Simp set scsi-controller-regex 22139027Sbrueffer "(aac|adv|adw|aha|ahb|ahc|ahd|aic|amd|amr|asr|bt|ciss|ct|dpt|\ 23146969Smarius esp|ida|iir|ips|isp|mlx|mly|mpt|ncr|ncv|nsp|stg|sym|trm|wds)\ 24139027Sbrueffer [0-9]+"; 25108983Simp}; 26108983Simp 27108983Simp# Note that the attach/detach with the highest value wins, so that one can 28108983Simp# override these general rules. 29108983Simp 30108983Simp# 31159126Sthompsa# Configure the interface on attach. Due to a historical accident, this 32159126Sthompsa# script is called pccard_ether. 33108983Simp# 34187743Ssam# NB: DETACH events are ignored; the kernel should handle all cleanup 35187743Ssam# (routes, arp cache) if you need to do something beware of races 36187743Ssam# against immediate create of a device w/ the same name; e.g. 37187743Ssam# ifconfig bridge0 destroy; ifconfig bridge0 create 38187743Ssam# 39159126Sthompsanotify 0 { 40159126Sthompsa match "system" "IFNET"; 41159126Sthompsa match "type" "ATTACH"; 42159126Sthompsa action "/etc/pccard_ether $subsystem start"; 43108983Simp}; 44108983Simp 45147088Sbrooks# 46147088Sbrooks# Try to start dhclient on Ethernet like interfaces when the link comes 47147088Sbrooks# up. Only devices that are configured to support DHCP will actually 48147088Sbrooks# run it. No link down rule exists because dhclient automaticly exits 49147088Sbrooks# when the link goes down. 50147088Sbrooks# 51147088Sbrooksnotify 0 { 52147088Sbrooks match "system" "IFNET"; 53147088Sbrooks match "type" "LINK_UP"; 54148642Ssam media-type "ethernet"; 55175683Smtm action "/etc/rc.d/dhclient quietstart $subsystem"; 56147088Sbrooks}; 57147088Sbrooks 58148642Ssam# 59148642Ssam# Like Ethernet devices, but separate because 60148642Ssam# they have a different media type. We may want 61148642Ssam# to exploit this later. 62148642Ssam# 63148642Ssamdetach 0 { 64148642Ssam media-type "802.11"; 65148642Ssam action "/etc/pccard_ether $device-name stop"; 66148642Ssam}; 67148642Ssamattach 0 { 68148642Ssam media-type "802.11"; 69148642Ssam action "/etc/pccard_ether $device-name start"; 70148642Ssam}; 71148642Ssamnotify 0 { 72148642Ssam match "system" "IFNET"; 73148642Ssam match "type" "LINK_UP"; 74148642Ssam media-type "802.11"; 75175683Smtm action "/etc/rc.d/dhclient quietstart $subsystem"; 76148642Ssam}; 77148642Ssam 78108983Simp# An entry like this might be in a different file, but is included here 79108983Simp# as an example of how to override things. Normally 'ed50' would match 80108983Simp# the above attach/detach stuff, but the value of 100 makes it 81139281Sbrueffer# hard wired to 1.2.3.4. 82108983Simpattach 100 { 83108983Simp device-name "ed50"; 84108983Simp action "ifconfig $device-name inet 1.2.3.4 netmask 0xffff0000"; 85108983Simp}; 86108983Simpdetach 100 { 87108983Simp device-name "ed50"; 88108983Simp}; 89108983Simp 90152326Semax# When a USB Bluetooth dongle appears activate it 91152326Semaxattach 100 { 92152326Semax device-name "ubt[0-9]+"; 93175683Smtm action "/etc/rc.d/bluetooth quietstart $device-name"; 94152326Semax}; 95152326Semaxdetach 100 { 96152326Semax device-name "ubt[0-9]+"; 97175683Smtm action "/etc/rc.d/bluetooth quietstop $device-name"; 98152326Semax}; 99152326Semax 100139281Sbrueffer# When a USB keyboard arrives, attach it as the console keyboard. 101134584Sbrooksattach 100 { 102134584Sbrooks device-name "ukbd0"; 103156782Semax action "/etc/rc.d/syscons setkeyboard /dev/ukbd0"; 104134584Sbrooks}; 105134584Sbrooksdetach 100 { 106134584Sbrooks device-name "ukbd0"; 107156331Semax action "/etc/rc.d/syscons setkeyboard /dev/kbd0"; 108134584Sbrooks}; 109134584Sbrooks 110138175Siedowseattach 100 { 111138175Siedowse device-name "ums[0-9]+"; 112175683Smtm action "/etc/rc.d/moused quietstart $device-name"; 113138175Siedowse}; 114138175Siedowse 115179804Skmacydetach 100 { 116179804Skmacy device-name "ums[0-9]+"; 117179804Skmacy action "/etc/rc.d/moused stop $device-name"; 118179804Skmacy}; 119179804Skmacy 120153300Siedowse# Firmware download into the ActiveWire board. After the firmware download is 121153300Siedowse# done the device detaches and reappears as something new and shiny 122153300Siedowse# automatically. 123153300Siedowseattach 100 { 124153300Siedowse match "vendor" "0x0854"; 125153300Siedowse match "product" "0x0100"; 126153300Siedowse match "release" "0x0000"; 127153300Siedowse action "/usr/local/bin/ezdownload -f /usr/local/share/usb/firmware/0854.0100.0_01.hex $device-name"; 128153300Siedowse}; 129153300Siedowse 130153300Siedowse# Firmware download for Entrega Serial DB25 adapter. 131153300Siedowseattach 100 { 132153300Siedowse match "vendor" "0x1645"; 133153300Siedowse match "product" "0x8001"; 134153300Siedowse match "release" "0x0101"; 135192198Smaxim 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"; 136153300Siedowse}; 137153300Siedowse 138153300Siedowse# This entry starts the ColdSync tool in daemon mode. Make sure you have an up 139153300Siedowse# to date /usr/local/etc/palms. We override the 'listen' settings for port and 140153300Siedowse# type in /usr/local/etc/coldsync.conf. 141207020Sthompsanotify 100 { 142207020Sthompsa match "system" "USB"; 143207020Sthompsa match "subsystem" "DEVICE"; 144207020Sthompsa match "type" "ATTACH"; 145207020Sthompsa match "vendor" "0x082d"; 146207020Sthompsa match "product" "0x0100"; 147207020Sthompsa match "release" "0x0100"; 148207020Sthompsa action "/usr/local/bin/coldsync -md -p /dev/$cdev -t usb"; 149153300Siedowse}; 150153300Siedowse 151108983Simp# 152148471Simp# Rescan scsi device-names on attach, but not detach. However, it is 153148471Simp# disabled by default due to reports of problems. 154108983Simp# 155108983Simpattach 0 { 156108983Simp device-name "$scsi-controller-regex"; 157131646Simp// action "camcontrol rescan all"; 158108983Simp}; 159108983Simp 160108983Simp# Don't even try to second guess what to do about drivers that don't 161114799Simp# match here. Instead, pass it off to syslog. Commented out for the 162166754Simp# moment, as the pnpinfo variable isn't set in devd yet. Individual 163166754Simp# variables within the bus supplied pnpinfo are set. 164119254Simpnomatch 0 { 165114852Simp# action "logger Unknown device: $pnpinfo $location $bus"; 166119254Simp}; 167108983Simp 168166701Sjoerg# Various logging of unknown devices. 169166701Sjoergnomatch 10 { 170166701Sjoerg match "bus" "uhub[0-9]+"; 171166701Sjoerg action "logger Unknown USB device: vendor $vendor product $product \ 172166701Sjoerg bus $bus"; 173166701Sjoerg}; 174166701Sjoerg 175166701Sjoerg# Some PC-CARDs don't offer numerical manufacturer/product IDs, just 176166701Sjoerg# show the CIS info there. 177166701Sjoergnomatch 20 { 178166701Sjoerg match "bus" "pccard[0-9]+"; 179166701Sjoerg match "manufacturer" "0xffffffff"; 180166701Sjoerg match "product" "0xffffffff"; 181166701Sjoerg action "logger Unknown PCCARD device: CISproduct $cisproduct \ 182166701Sjoerg CIS-vendor $cisvendor bus $bus"; 183166701Sjoerg}; 184166701Sjoerg 185166701Sjoergnomatch 10 { 186166701Sjoerg match "bus" "pccard[0-9]+"; 187166701Sjoerg action "logger Unknown PCCARD device: manufacturer $manufacturer \ 188166701Sjoerg product $product CISproduct $cisproduct CIS-vendor \ 189166701Sjoerg $cisvendor bus $bus"; 190166701Sjoerg}; 191166701Sjoerg 192166701Sjoergnomatch 10 { 193166701Sjoerg match "bus" "cardbus[0-9]+"; 194166701Sjoerg action "logger Unknown Cardbus device: device $device class $class \ 195166701Sjoerg vendor $vendor bus $bus"; 196166701Sjoerg}; 197166701Sjoerg 198139281Sbrueffer# Switch power profiles when the AC line state changes. 199123626Snjlnotify 10 { 200123626Snjl match "system" "ACPI"; 201123626Snjl match "subsystem" "ACAD"; 202125366Snjl action "/etc/rc.d/power_profile $notify"; 203123626Snjl}; 204123626Snjl 205125366Snjl# Notify all users before beginning emergency shutdown when we get 206125366Snjl# a _CRT or _HOT thermal event and we're going to power down the system 207125366Snjl# very soon. 208125366Snjlnotify 10 { 209125366Snjl match "system" "ACPI"; 210125366Snjl match "subsystem" "Thermal"; 211125366Snjl match "notify" "0xcc"; 212125366Snjl action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'"; 213125366Snjl}; 214125366Snjl 215168495Spjd# Sample ZFS problem reports handling. 216168495Spjdnotify 10 { 217168495Spjd match "system" "ZFS"; 218168495Spjd match "type" "zpool"; 219168495Spjd action "logger -p kern.err 'ZFS: failed to load zpool $pool'"; 220168495Spjd}; 221168495Spjd 222168495Spjdnotify 10 { 223168495Spjd match "system" "ZFS"; 224168495Spjd match "type" "vdev"; 225168497Spjd action "logger -p kern.err 'ZFS: vdev failure, zpool=$pool type=$type'"; 226168495Spjd}; 227168495Spjd 228168495Spjdnotify 10 { 229168495Spjd match "system" "ZFS"; 230168495Spjd match "type" "data"; 231168495Spjd action "logger -p kern.warn 'ZFS: zpool I/O failure, zpool=$pool error=$zio_err'"; 232168495Spjd}; 233168495Spjd 234168495Spjdnotify 10 { 235168495Spjd match "system" "ZFS"; 236168495Spjd match "type" "io"; 237168495Spjd action "logger -p kern.warn 'ZFS: vdev I/O failure, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size error=$zio_err'"; 238168495Spjd}; 239168495Spjd 240168495Spjdnotify 10 { 241168495Spjd match "system" "ZFS"; 242168495Spjd match "type" "checksum"; 243168495Spjd action "logger -p kern.warn 'ZFS: checksum mismatch, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size'"; 244168495Spjd}; 245168495Spjd 246170976Snjl# User requested suspend, so perform preparation steps and then execute 247170976Snjl# the actual suspend process. 248170976Snjlnotify 10 { 249170976Snjl match "system" "ACPI"; 250170976Snjl match "subsystem" "Suspend"; 251170976Snjl action "/etc/rc.suspend acpi $notify"; 252170976Snjl}; 253170976Snjlnotify 10 { 254170976Snjl match "system" "ACPI"; 255170976Snjl match "subsystem" "Resume"; 256170976Snjl action "/etc/rc.resume acpi $notify"; 257170976Snjl}; 258170976Snjl 259108983Simp/* EXAMPLES TO END OF FILE 260108983Simp 261108983Simp# The following might be an example of something that a vendor might 262108983Simp# install if you were to add their device. This might reside in 263108983Simp# /usr/local/etc/devd/deqna.conf. A deqna is, in this hypothetical 264108983Simp# example, a pccard ethernet-like device. Students of history may 265108983Simp# know other devices by this name, and will get the in-jokes in this 266108983Simp# entry. 267108983Simpnomatch 10 { 268108983Simp match "bus" "pccard[0-9]+"; 269108983Simp match "manufacturer" "0x1234"; 270108983Simp match "product" "0x2323"; 271108983Simp action "kldload if_deqna"; 272108983Simp}; 273108983Simpattach 10 { 274108983Simp device-name "deqna[0-9]+"; 275108983Simp action "/etc/pccard_ether $device-name start"; 276108983Simp}; 277108983Simpdetach 10 { 278108983Simp device-name "deqna[0-9]+"; 279108983Simp action "/etc/pccard_ether $device-name stop"; 280108983Simp}; 281108983Simp 282121493Snjl# Examples of notify hooks. A notify is a generic way for a kernel 283121493Snjl# subsystem to send event notification to userland. 284121493Snjl# 285121493Snjl# Here are some examples of ACPI notify handlers. ACPI subsystems that 286121493Snjl# generate notifies include the AC adapter, power/sleep buttons, 287121493Snjl# control method batteries, lid switch, and thermal zones. 288121493Snjl# 289121493Snjl# Information returned is not always the same as the ACPI notify 290121493Snjl# events. See the ACPI specification for more information about 291121493Snjl# notifies. Here is the information returned for each subsystem: 292121493Snjl# 293121493Snjl# ACAD: AC line state (0 is offline, 1 is online) 294121493Snjl# Button: Button pressed (0 for power, 1 for sleep) 295121493Snjl# CMBAT: ACPI battery events 296121493Snjl# Lid: Lid state (0 is closed, 1 is open) 297170976Snjl# Suspend, Resume: Suspend and resume notification 298121493Snjl# Thermal: ACPI thermal zone events 299121493Snjl# 300121493Snjl# This example calls a script when the AC state changes, passing the 301121493Snjl# notify value as the first argument. If the state is 0x00, it might 302121493Snjl# call some sysctls to implement economy mode. If 0x01, it might set 303121493Snjl# the mode to performance. 304121493Snjlnotify 10 { 305121493Snjl match "system" "ACPI"; 306121493Snjl match "subsystem" "ACAD"; 307121493Snjl action "/etc/acpi_ac $notify"; 308121493Snjl}; 309108983Simp*/ 310