devd.conf revision 139027
1# $FreeBSD: head/etc/devd.conf 139027 2004-12-19 00:50:07Z brueffer $ 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|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 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, the default is to run dhclient. 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# An entry like this might be in a different file, but is included here 49# as an example of how to override things. Normally 'ed50' would match 50# the above attach/detach stuff, but the value of 100 makes it 51# ed50 is hard wired to 1.2.3.4 52attach 100 { 53 device-name "ed50"; 54 action "ifconfig $device-name inet 1.2.3.4 netmask 0xffff0000"; 55}; 56detach 100 { 57 device-name "ed50"; 58}; 59 60# When a USB keyboard arrives, attach it as the console keyboard 61attach 100 { 62 device-name "ukbd0"; 63 action "test -c /dev/kbd1 && kbdcontrol -k /dev/kbd1 < /dev/console"; 64}; 65detach 100 { 66 device-name "ukbd0"; 67 action "kbdcontrol -k /dev/kbd0 < /dev/console"; 68}; 69 70# The entry below starts moused when a mouse is plugged in. Moused 71# stops automatically (actually it bombs :) when the device disappears. 72attach 100 { 73 device-name "ums[0-9]+"; 74 action "/etc/rc.d/moused start $device-name"; 75}; 76 77# 78# Rescan scsi device-names on attach, but not detach. 79# 80attach 0 { 81 device-name "$scsi-controller-regex"; 82// action "camcontrol rescan all"; 83}; 84 85# Don't even try to second guess what to do about drivers that don't 86# match here. Instead, pass it off to syslog. Commented out for the 87# moment, as pnpinfo isn't set in devd yet 88nomatch 0 { 89# action "logger Unknown device: $pnpinfo $location $bus"; 90}; 91 92# Switch power profiles when the AC line state changes 93notify 10 { 94 match "system" "ACPI"; 95 match "subsystem" "ACAD"; 96 action "/etc/rc.d/power_profile $notify"; 97}; 98 99# Notify all users before beginning emergency shutdown when we get 100# a _CRT or _HOT thermal event and we're going to power down the system 101# very soon. 102notify 10 { 103 match "system" "ACPI"; 104 match "subsystem" "Thermal"; 105 match "notify" "0xcc"; 106 action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'"; 107}; 108 109/* EXAMPLES TO END OF FILE 110 111# The following might be an example of something that a vendor might 112# install if you were to add their device. This might reside in 113# /usr/local/etc/devd/deqna.conf. A deqna is, in this hypothetical 114# example, a pccard ethernet-like device. Students of history may 115# know other devices by this name, and will get the in-jokes in this 116# entry. 117nomatch 10 { 118 match "bus" "pccard[0-9]+"; 119 match "manufacturer" "0x1234"; 120 match "product" "0x2323"; 121 action "kldload if_deqna"; 122}; 123attach 10 { 124 device-name "deqna[0-9]+"; 125 action "/etc/pccard_ether $device-name start"; 126}; 127detach 10 { 128 device-name "deqna[0-9]+"; 129 action "/etc/pccard_ether $device-name stop"; 130}; 131 132# Examples of notify hooks. A notify is a generic way for a kernel 133# subsystem to send event notification to userland. 134# 135# Here are some examples of ACPI notify handlers. ACPI subsystems that 136# generate notifies include the AC adapter, power/sleep buttons, 137# control method batteries, lid switch, and thermal zones. 138# 139# Information returned is not always the same as the ACPI notify 140# events. See the ACPI specification for more information about 141# notifies. Here is the information returned for each subsystem: 142# 143# ACAD: AC line state (0 is offline, 1 is online) 144# Button: Button pressed (0 for power, 1 for sleep) 145# CMBAT: ACPI battery events 146# Lid: Lid state (0 is closed, 1 is open) 147# Thermal: ACPI thermal zone events 148# 149# This example calls a script when the AC state changes, passing the 150# notify value as the first argument. If the state is 0x00, it might 151# call some sysctls to implement economy mode. If 0x01, it might set 152# the mode to performance. 153notify 10 { 154 match "system" "ACPI"; 155 match "subsystem" "ACAD"; 156 action "/etc/acpi_ac $notify"; 157}; 158*/ 159