devd.conf (168497) | devd.conf (170976) |
---|---|
1# $FreeBSD: head/etc/devd.conf 168497 2007-04-08 16:05:23Z pjd $ | 1# $FreeBSD: head/etc/devd.conf 170976 2007-06-21 22:50:37Z njl $ |
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 --- 224 unchanged lines hidden (view full) --- 234}; 235 236notify 10 { 237 match "system" "ZFS"; 238 match "type" "checksum"; 239 action "logger -p kern.warn 'ZFS: checksum mismatch, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size'"; 240}; 241 | 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 --- 224 unchanged lines hidden (view full) --- 234}; 235 236notify 10 { 237 match "system" "ZFS"; 238 match "type" "checksum"; 239 action "logger -p kern.warn 'ZFS: checksum mismatch, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size'"; 240}; 241 |
242# User requested suspend, so perform preparation steps and then execute 243# the actual suspend process. 244notify 10 { 245 match "system" "ACPI"; 246 match "subsystem" "Suspend"; 247 action "/etc/rc.suspend acpi $notify"; 248}; 249notify 10 { 250 match "system" "ACPI"; 251 match "subsystem" "Resume"; 252 action "/etc/rc.resume acpi $notify"; 253}; 254 |
|
242/* EXAMPLES TO END OF FILE 243 244# The following might be an example of something that a vendor might 245# install if you were to add their device. This might reside in 246# /usr/local/etc/devd/deqna.conf. A deqna is, in this hypothetical 247# example, a pccard ethernet-like device. Students of history may 248# know other devices by this name, and will get the in-jokes in this 249# entry. --- 22 unchanged lines hidden (view full) --- 272# Information returned is not always the same as the ACPI notify 273# events. See the ACPI specification for more information about 274# notifies. Here is the information returned for each subsystem: 275# 276# ACAD: AC line state (0 is offline, 1 is online) 277# Button: Button pressed (0 for power, 1 for sleep) 278# CMBAT: ACPI battery events 279# Lid: Lid state (0 is closed, 1 is open) | 255/* EXAMPLES TO END OF FILE 256 257# The following might be an example of something that a vendor might 258# install if you were to add their device. This might reside in 259# /usr/local/etc/devd/deqna.conf. A deqna is, in this hypothetical 260# example, a pccard ethernet-like device. Students of history may 261# know other devices by this name, and will get the in-jokes in this 262# entry. --- 22 unchanged lines hidden (view full) --- 285# Information returned is not always the same as the ACPI notify 286# events. See the ACPI specification for more information about 287# notifies. Here is the information returned for each subsystem: 288# 289# ACAD: AC line state (0 is offline, 1 is online) 290# Button: Button pressed (0 for power, 1 for sleep) 291# CMBAT: ACPI battery events 292# Lid: Lid state (0 is closed, 1 is open) |
293# Suspend, Resume: Suspend and resume notification |
|
280# Thermal: ACPI thermal zone events 281# 282# This example calls a script when the AC state changes, passing the 283# notify value as the first argument. If the state is 0x00, it might 284# call some sysctls to implement economy mode. If 0x01, it might set 285# the mode to performance. 286notify 10 { 287 match "system" "ACPI"; 288 match "subsystem" "ACAD"; 289 action "/etc/acpi_ac $notify"; 290}; 291*/ | 294# Thermal: ACPI thermal zone events 295# 296# This example calls a script when the AC state changes, passing the 297# notify value as the first argument. If the state is 0x00, it might 298# call some sysctls to implement economy mode. If 0x01, it might set 299# the mode to performance. 300notify 10 { 301 match "system" "ACPI"; 302 match "subsystem" "ACAD"; 303 action "/etc/acpi_ac $notify"; 304}; 305*/ |