devd.conf revision 147088
1# $FreeBSD: head/etc/devd.conf 147088 2005-06-07 04:49:12Z brooks $ 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 set ethernet-nic-regex 21 "(an|ar|ath|aue|awi|axe|bfe|bge|cdce|cm|cnw|cs|cue|dc|de|ed|el|em|\ 22 ep|ex|fe|fxp|gem|hme|ie|kue|lge|lnc|my|nge|pcn|ray|re|rl|rue|\ 23 sf|sis|sk|sn|snc|ste|ti|tl|tx|txp|udav|vge|vr|vx|wb|wi|xe|xl)\ 24 [0-9]+"; 25 set scsi-controller-regex 26 "(aac|adv|adw|aha|ahb|ahc|ahd|aic|amd|amr|asr|bt|ciss|ct|dpt|\ 27 esp|ida|iir|ips|isp|mlx|mly|mpt|ncr|ncv|nsp|stg|sym|trm|wds)\ 28 [0-9]+"; 29}; 30 31# Note that the attach/detach with the highest value wins, so that one can 32# override these general rules. 33 34# 35# For ethernet like devices start configuring the interface. Due to 36# a historical accident, this script is called pccard_ether. 37# 38attach 0 { 39 device-name "$ethernet-nic-regex"; 40 action "/etc/pccard_ether $device-name start"; 41}; 42 43detach 0 { 44 device-name "$ethernet-nic-regex"; 45 action "/etc/pccard_ether $device-name stop"; 46}; 47 48# 49# Try to start dhclient on Ethernet like interfaces when the link comes 50# up. Only devices that are configured to support DHCP will actually 51# run it. No link down rule exists because dhclient automaticly exits 52# when the link goes down. 53# 54notify 0 { 55 match "system" "IFNET"; 56 match "subsystem" "$ethernet-nic-regex"; 57 match "type" "LINK_UP"; 58 action "/etc/rc.d/dhclient start $subsystem"; 59}; 60 61# An entry like this might be in a different file, but is included here 62# as an example of how to override things. Normally 'ed50' would match 63# the above attach/detach stuff, but the value of 100 makes it 64# hard wired to 1.2.3.4. 65attach 100 { 66 device-name "ed50"; 67 action "ifconfig $device-name inet 1.2.3.4 netmask 0xffff0000"; 68}; 69detach 100 { 70 device-name "ed50"; 71}; 72 73# When a USB keyboard arrives, attach it as the console keyboard. 74attach 100 { 75 device-name "ukbd0"; 76 action "kbdcontrol -k /dev/ukbd0 < /dev/console && /etc/rc.d/syscons restart"; 77}; 78detach 100 { 79 device-name "ukbd0"; 80 action "kbdcontrol -k /dev/kbd0 < /dev/console"; 81}; 82 83# The entry below starts moused when a mouse is plugged in. Moused 84# stops automatically (actually it bombs :) when the device disappears. 85attach 100 { 86 device-name "ums[0-9]+"; 87 action "/etc/rc.d/moused start $device-name"; 88}; 89 90# 91# Rescan scsi device-names on attach, but not detach. 92# 93attach 0 { 94 device-name "$scsi-controller-regex"; 95// action "camcontrol rescan all"; 96}; 97 98# Don't even try to second guess what to do about drivers that don't 99# match here. Instead, pass it off to syslog. Commented out for the 100# moment, as pnpinfo isn't set in devd yet. 101nomatch 0 { 102# action "logger Unknown device: $pnpinfo $location $bus"; 103}; 104 105# Switch power profiles when the AC line state changes. 106notify 10 { 107 match "system" "ACPI"; 108 match "subsystem" "ACAD"; 109 action "/etc/rc.d/power_profile $notify"; 110}; 111 112# Notify all users before beginning emergency shutdown when we get 113# a _CRT or _HOT thermal event and we're going to power down the system 114# very soon. 115notify 10 { 116 match "system" "ACPI"; 117 match "subsystem" "Thermal"; 118 match "notify" "0xcc"; 119 action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'"; 120}; 121 122/* EXAMPLES TO END OF FILE 123 124# The following might be an example of something that a vendor might 125# install if you were to add their device. This might reside in 126# /usr/local/etc/devd/deqna.conf. A deqna is, in this hypothetical 127# example, a pccard ethernet-like device. Students of history may 128# know other devices by this name, and will get the in-jokes in this 129# entry. 130nomatch 10 { 131 match "bus" "pccard[0-9]+"; 132 match "manufacturer" "0x1234"; 133 match "product" "0x2323"; 134 action "kldload if_deqna"; 135}; 136attach 10 { 137 device-name "deqna[0-9]+"; 138 action "/etc/pccard_ether $device-name start"; 139}; 140detach 10 { 141 device-name "deqna[0-9]+"; 142 action "/etc/pccard_ether $device-name stop"; 143}; 144 145# Examples of notify hooks. A notify is a generic way for a kernel 146# subsystem to send event notification to userland. 147# 148# Here are some examples of ACPI notify handlers. ACPI subsystems that 149# generate notifies include the AC adapter, power/sleep buttons, 150# control method batteries, lid switch, and thermal zones. 151# 152# Information returned is not always the same as the ACPI notify 153# events. See the ACPI specification for more information about 154# notifies. Here is the information returned for each subsystem: 155# 156# ACAD: AC line state (0 is offline, 1 is online) 157# Button: Button pressed (0 for power, 1 for sleep) 158# CMBAT: ACPI battery events 159# Lid: Lid state (0 is closed, 1 is open) 160# Thermal: ACPI thermal zone events 161# 162# This example calls a script when the AC state changes, passing the 163# notify value as the first argument. If the state is 0x00, it might 164# call some sysctls to implement economy mode. If 0x01, it might set 165# the mode to performance. 166notify 10 { 167 match "system" "ACPI"; 168 match "subsystem" "ACAD"; 169 action "/etc/acpi_ac $notify"; 170}; 171*/ 172