devd.conf revision 152326
1# $FreeBSD: head/etc/devd.conf 152326 2005-11-12 03:42:56Z emax $ 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# For ethernet like devices start configuring the interface. Due to 32# a historical accident, this script is called pccard_ether. 33# 34attach 0 { 35 media-type "ethernet"; 36 action "/etc/pccard_ether $device-name start"; 37}; 38 39detach 0 { 40 media-type "ethernet"; 41 action "/etc/pccard_ether $device-name stop"; 42}; 43 44# 45# Try to start dhclient on Ethernet like interfaces when the link comes 46# up. Only devices that are configured to support DHCP will actually 47# run it. No link down rule exists because dhclient automaticly exits 48# when the link goes down. 49# 50notify 0 { 51 match "system" "IFNET"; 52 match "type" "LINK_UP"; 53 media-type "ethernet"; 54 action "/etc/rc.d/dhclient start $subsystem"; 55}; 56 57# 58# Like Ethernet devices, but separate because 59# they have a different media type. We may want 60# to exploit this later. 61# 62detach 0 { 63 media-type "802.11"; 64 action "/etc/pccard_ether $device-name stop"; 65}; 66attach 0 { 67 media-type "802.11"; 68 action "/etc/pccard_ether $device-name start"; 69}; 70notify 0 { 71 match "system" "IFNET"; 72 match "type" "LINK_UP"; 73 media-type "802.11"; 74 action "/etc/rc.d/dhclient start $subsystem"; 75}; 76 77# An entry like this might be in a different file, but is included here 78# as an example of how to override things. Normally 'ed50' would match 79# the above attach/detach stuff, but the value of 100 makes it 80# hard wired to 1.2.3.4. 81attach 100 { 82 device-name "ed50"; 83 action "ifconfig $device-name inet 1.2.3.4 netmask 0xffff0000"; 84}; 85detach 100 { 86 device-name "ed50"; 87}; 88 89# When a USB Bluetooth dongle appears activate it 90attach 100 { 91 device-name "ubt[0-9]+"; 92 action "/etc/rc.d/bluetooth start $device-name"; 93}; 94detach 100 { 95 device-name "ubt[0-9]+"; 96 action "/etc/rc.d/bluetooth stop $device-name"; 97}; 98 99# When a USB keyboard arrives, attach it as the console keyboard. 100attach 100 { 101 device-name "ukbd0"; 102 action "kbdcontrol -k /dev/ukbd0 < /dev/console && /etc/rc.d/syscons restart"; 103}; 104detach 100 { 105 device-name "ukbd0"; 106 action "kbdcontrol -k /dev/kbd0 < /dev/console"; 107}; 108 109# The entry below starts moused when a mouse is plugged in. Moused 110# stops automatically (actually it bombs :) when the device disappears. 111attach 100 { 112 device-name "ums[0-9]+"; 113 action "/etc/rc.d/moused start $device-name"; 114}; 115 116# 117# Rescan scsi device-names on attach, but not detach. However, it is 118# disabled by default due to reports of problems. 119# 120attach 0 { 121 device-name "$scsi-controller-regex"; 122// action "camcontrol rescan all"; 123}; 124 125# Don't even try to second guess what to do about drivers that don't 126# match here. Instead, pass it off to syslog. Commented out for the 127# moment, as pnpinfo isn't set in devd yet. 128nomatch 0 { 129# action "logger Unknown device: $pnpinfo $location $bus"; 130}; 131 132# Switch power profiles when the AC line state changes. 133notify 10 { 134 match "system" "ACPI"; 135 match "subsystem" "ACAD"; 136 action "/etc/rc.d/power_profile $notify"; 137}; 138 139# Notify all users before beginning emergency shutdown when we get 140# a _CRT or _HOT thermal event and we're going to power down the system 141# very soon. 142notify 10 { 143 match "system" "ACPI"; 144 match "subsystem" "Thermal"; 145 match "notify" "0xcc"; 146 action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'"; 147}; 148 149/* EXAMPLES TO END OF FILE 150 151# The following might be an example of something that a vendor might 152# install if you were to add their device. This might reside in 153# /usr/local/etc/devd/deqna.conf. A deqna is, in this hypothetical 154# example, a pccard ethernet-like device. Students of history may 155# know other devices by this name, and will get the in-jokes in this 156# entry. 157nomatch 10 { 158 match "bus" "pccard[0-9]+"; 159 match "manufacturer" "0x1234"; 160 match "product" "0x2323"; 161 action "kldload if_deqna"; 162}; 163attach 10 { 164 device-name "deqna[0-9]+"; 165 action "/etc/pccard_ether $device-name start"; 166}; 167detach 10 { 168 device-name "deqna[0-9]+"; 169 action "/etc/pccard_ether $device-name stop"; 170}; 171 172# Examples of notify hooks. A notify is a generic way for a kernel 173# subsystem to send event notification to userland. 174# 175# Here are some examples of ACPI notify handlers. ACPI subsystems that 176# generate notifies include the AC adapter, power/sleep buttons, 177# control method batteries, lid switch, and thermal zones. 178# 179# Information returned is not always the same as the ACPI notify 180# events. See the ACPI specification for more information about 181# notifies. Here is the information returned for each subsystem: 182# 183# ACAD: AC line state (0 is offline, 1 is online) 184# Button: Button pressed (0 for power, 1 for sleep) 185# CMBAT: ACPI battery events 186# Lid: Lid state (0 is closed, 1 is open) 187# Thermal: ACPI thermal zone events 188# 189# This example calls a script when the AC state changes, passing the 190# notify value as the first argument. If the state is 0x00, it might 191# call some sysctls to implement economy mode. If 0x01, it might set 192# the mode to performance. 193notify 10 { 194 match "system" "ACPI"; 195 match "subsystem" "ACAD"; 196 action "/etc/acpi_ac $notify"; 197}; 198*/ 199