9 More Discussions You Might Find Interesting
1. Programming
On the NI-VISA boards there has been some frustration where folks cannot get NI-VISA to work on macOS Catalina because Catalina (macOS 10.15.x) is "not supported" by NI-VISA (for many months, it seems). Currently, the README shows:
NI-VISA 19.0 for macOS supports the following platforms:
... (10 Replies)
Discussion started by: Neo
10 Replies
2. Shell Programming and Scripting
Hello,
I have a backup script that runs an rsync backup to an external drive. I use the script frequently on Windows and Linux and have installed it on a Mac. The script has an option to run shutdown after the backup has completed. Since backup can take hours to run, this is an option that is... (10 Replies)
Discussion started by: LMHmedchem
10 Replies
3. Shell Programming and Scripting
Hello,
I am running a bash script to do an rsync back on a computer running MacOS High Sierra. This is the script I am using,
#!/bin/bash
# main backup location, trailing slash included
backup_loc="/Volumes/Archive_Volume/00_macos_backup/"
# generic backup function
function backup {... (12 Replies)
Discussion started by: LMHmedchem
12 Replies
4. Shell Programming and Scripting
Hello,
I have the following script that just archives and clears some log files.
#!/bin/bash
# script: archive_logs_and_clear
# add date to logfile names and copy archive directory
# clear logs
# change to script directory
cd ... (4 Replies)
Discussion started by: LMHmedchem
4 Replies
5. OS X (Apple)
Some hackers found a security hole in macOS High Sierra and tweeted it to the world before telling Apple about the problem. You can see the details from PC Magazine's daily news here: Apple Releases Fix for MacOS High Sierra 'Root' Bug. The original story this morning was published before a patch... (6 Replies)
Discussion started by: Don Cragun
6 Replies
6. Solaris
I have a T5140 and cannot find the power switch -is there an on/off button? Good grief !
Thank you in advance.
joe (3 Replies)
Discussion started by: joboy
3 Replies
7. AIX
Hi,
This thread has been posted before on linuxquestions.org, but no answer, maybe because this is unix question and not linux. I'm posting the same thread here, hope I can get an answer from someone in the meantime, I wish I could post of emergency thread but it needs bits which I don't have :... (6 Replies)
Discussion started by: aLuViAn
6 Replies
8. UNIX for Dummies Questions & Answers
Please help me with this ...........
Suppose i have made a database of 25 people and want to make the user select any number of people till he wishes and then press a button to stop the process (of selecting)
what coding should be followed by me ...........:confused::confused: (1 Reply)
Discussion started by: doctor001
1 Replies
9. UNIX for Dummies Questions & Answers
I am trying to test input from the user, if they press enter with out an Y or N. I have the characheter thing sorted but when it comes to a blank or empty key press I am having trouble.
if ; then
clear
echo "Sorry, that is an invalid choice!"
exit
fi
I am using a KSH script in... (3 Replies)
Discussion started by: jagannatha
3 Replies
POWERD(8) BSD System Manager's Manual POWERD(8)
NAME
powerd -- power management daemon for sysmon
SYNOPSIS
powerd [-dn]
DESCRIPTION
powerd acts upon power management events posted by the kernel's power management facility. When events are posted, powerd translates the
event into a script name and a list of arguments. powerd then runs the script in order to implement the power management policy defined by
the system administrator.
powerd supports the following option:
-d Enable debugging mode. Verbose messages and all messages intended for syslog(8) will be sent to stderr, and powerd will stay in the
foreground of the controlling terminal.
-n Prevent execution of power management scripts.
CONFIGURATION SCRIPTS
All configuration of powerd is encapsulated into scripts that are run when power management events occur. The daemon will look for the
scripts from the directory /etc/powerd/scripts.
Configuration scripts are run synchronously; powerd will start the script and wait for its completion before it handles the next event.
Configuration scripts are called with different arguments, depending on the script class. These classes are described in the following sec-
tions.
POWER SWITCH SCRIPTS
Power switch scripts are called when a state change event occurs on a power switch device. Power switch scripts are called with two argu-
ments: the device with which the event is associated, and the event type.
The following power switch script names are defined:
power_button This script is called when an event occurs on a power button device.
reset_button This script is called when an event occurs on a reset button device.
sleep_button This script is called when an event occurs on a sleep button device.
lid_switch This script is called when an event occurs on a lid switch device.
acadapter This script is called when an online or offline event occurs on an AC adapter device.
hotkey_button This script is called when an event occurs on a hotkey button device.
The following events are defined for power switch devices:
pressed The button was pressed, the lid was closed, or the AC adapter was connected.
released The button was released, the lid was opened, or the AC adapter was disconnected. Note that power and sleep button devices
usually do not post this type of event.
The following is an example of how a power button script might be invoked when a power button is pressed by the operator:
/etc/powerd/scripts/power_button acpibut0 pressed
ENVSYS SCRIPTS
envsys(4) scripts are called when a condition was triggered in a sensor. These scripts are called with three arguments: the device associ-
ated, the event type, and the sensor's name. The sensor_drive and the sensor_battery scripts uses a fourth argument: state description.
The following envsys script names are defined:
sensor_battery This script is called when an event occurs on a battery sensor (Wh/Ah/Battery state).
sensor_drive This script is called when an event occurs on a drive sensor.
sensor_fan This script is called when an event occurs on a fan sensor.
sensor_indicator This script is called when an event ocurrs on a indicator/integer sensor.
sensor_power This script is called when an event occurs on a power sensor (W/Ampere).
sensor_resistance This script is called when an event occurs on a resistance sensor (Ohm).
sensor_temperature This script is called when an event occurs on a temperature sensor.
sensor_voltage This script is called when an event occurs on a voltage sensor.
The following events are defined for fan, indicator, power, resistance, temperature, and voltage sensors:
critical A critical condition was triggered.
critical-under A critical under condition was triggered.
critical-over A critical over condition was triggered.
warning-under A warning under condition was triggered.
warning-over A warning over condition was triggered.
The following event is defined for all scripts, but it is only sent if any of the previous events has been previously sent:
normal A normal state/capacity/condition was triggered.
The following events are defined only for battery sensors:
user-capacity Capacity dropped below the limit set by the user.
low-power System is running in low power. This implies that the AC adapter is disconnected and all batteries are in critical or
low capacity. The script shutdowns the system gracefully by default.
The following events are defined for drive and battery sensors:
state-changed The state of the sensor has been changed and it is not in the normal state.
The following is an example of how a temperature sensor script might be invoked when a critical over condition is triggered:
/etc/powerd/scripts/sensor_temperature lm0 critical-over "CPU Temp"
SEE ALSO
acpi(4), acpiacad(4), acpibut(4), acpilid(4), envsys(4), i386/apm(4)
HISTORY
powerd first appeared in NetBSD 2.0. Support to handle envsys(4) events appeared in NetBSD 5.0.
AUTHORS
powerd was written by Jason R. Thorpe <thorpej@wasabisystems.com> and contributed by Wasabi Systems, Inc.
Juan Romero Pardines added support to handle envsys(4) events.
BUGS
Due to its synchronous nature powerd cannot be trusted to handle events within a certain time.
BSD
December 15, 2010 BSD