

I was also confused by this. If it was an example it should say that.
Edit: in fact the examples should also be explained. It wasn’t immediately clear to me what city example they were using.


I was also confused by this. If it was an example it should say that.
Edit: in fact the examples should also be explained. It wasn’t immediately clear to me what city example they were using.


90w here, so 65kwh/mo. Tinyminimicro server. Three pi (5, 4, 3B), fiber gateway, Mikrotik router, switch and two APs. Plus power gear (managed PDU and UPS).


Ah, ok. Good luck with it!


Users in several sites report success with the bios-pw.org site. Example: https://www.ifixit.com/Answers/View/110108/How+can+I+reset+bios+password
They say you try 3+ times, until a code is shown. Plug the code into that site for a reset code.
I have no idea if this is reliable or safe. Proceed at your own risk!
It’s a lot. But here are my most recent notes.
Note that the pipe & lock locations different by distro, as does the nut username. So these files won’t drop in and work anywhere.
The dummy driver will need to be installed and configured.
Mine also have several layers of timers on battery an online:
Most configs would have the client side cancel their timers if power returns. In my case I don’t want that because I prefer more certainty of state so that I know it’s safe to power cycle an outlet to bring a device back up. My NUT server runs on an old pi 3b with a read-only file system. So it never needs a safe shutdown. It’s the last man standing to bring everything else back up if the UPS returns to line power before the battery is exhausted. That’s why there is no local shutdown on the NUT server config.
Each snmpset... is a truncated version of an outlet power command.
Also, the wall commands were a debug aid. Uncomment to use, but test a command first. Wall doesn’t work on some distros.
NUT.CONF:
MODE=netserver
UPS.CONF:
[ups]
desc = My UPS
driver = dummy-ups
port = /opt/ups/ups.seq
UPSD.CONF:
LISTEN 0.0.0.0 3493
## all interfaces
## STATEPATH /var/run/nut
UPSD.USERS:
[upsuser]
password = <pw>
actions = set
upsmon master
[upssrv]
password = <pw>
actions = set
upsmon slave
[upspi]
password = <pw>
actions = set
upsmon slave
UPSMON.CONF:
RUN_AS_USER nut
#RUN_AS_USER root
MONITOR ups@localhost 1 upsuser <pw> master
NOTIFYMSG ONLINE "UPS %s on line power"
NOTIFYMSG ONBATT "UPS %s on battery"
NOTIFYMSG LOWBATT "UPS %s battery is low"
NOTIFYMSG FSD "UPS %s: forced shutdown in progress"
NOTIFYMSG COMMOK "Communications with UPS %s established"
NOTIFYMSG COMMBAD "Communications with UPS %s lost"
NOTIFYMSG SHUTDOWN "Auto logout and shutdown proceeding"
NOTIFYMSG REPLBATT "UPS %s battery needs to be replaced"
NOTIFYMSG NOCOMM "UPS %s is unavailable"
NOTIFYMSG NOPARENT "upsmon parent process died - shutdown impossible"
NOTIFYFLAG ONLINE WALL+EXEC+SYSLOG
NOTIFYFLAG ONBATT WALL+EXEC+SYSLOG
NOTIFYFLAG LOWBATT SYSLOG+WALL
NOTIFYFLAG FSD SYSLOG+WALL
NOTIFYFLAG COMMOK SYSLOG+WALL
NOTIFYFLAG COMMBAD SYSLOG+WALL
NOTIFYFLAG SHUTDOWN SYSLOG+WALL
NOTIFYFLAG REPLBATT SYSLOG+WALL
NOTIFYFLAG NOCOMM SYSLOG+WALL
NOTIFYFLAG NOPARENT SYSLOG+WALL
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -P +0"
NOTIFYCMD "/usr/sbin/upssched"
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME 15
# POWERDOWNFLAG /var/run/killpower
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 5
CERTVERIFY 0
FORCESSL 0
UPSSCHED.CONF:
CMDSCRIPT /etc/nut/upssched-cmd
PIPEFN /var/run/nut/upssched.pipe
LOCKFN /var/run/nut/upssched.lock
AT ONBATT ups@localhost CANCEL-TIMER online3
AT ONBATT ups@localhost CANCEL-TIMER online10
AT ONBATT ups@localhost START-TIMER onbatt5 300
AT ONBATT ups@localhost EXECUTE onbattnotify
AT ONLINE ups@localhost CANCEL-TIMER onbatt5
AT ONLINE ups@localhost START-TIMER online3 180
AT ONLINE ups@localhost START-TIMER online10 600
AT ONLINE ups@localhost EXECUTE onlinenotify
UPSSCHED-CMD
#! /bin/bash
#
# This script should be called by upssched via the CMDSCRIPT directive
# The first argument passed to your CMDSCRIPT is the name of the timer
# from your AT lines.
logger -t upssched-cmd "Calling upssched-cmd $1"
wall "Calling upssched-cmd $1"
UPS="ups@localhost"
HOST=$( uname -n)
TIMESTAMP=$(date +%Y%m%d%H%M%S)
STATUS=$( upsc $UPS ups.status )
CHARGE=$( upsc $UPS battery.charge )
CHMSG="UPS[STATUS]:$CHARGE%"
case $1 in
onbattnotify)
# srv and pi are upsmon clients and will shut down on their own after a 30s delay.
# Log the Notification.
logger -t upssched-cmd "UPS on Battery Power. Servers will shutdown in 30 seconds. Switch shutdown in 5 minutes. $CHMSG $TIMESTAMP"
wall "upssched-cmd onbattnotify: UPS on Battery Power. Servers will shutdown in 30 seconds. Switch shutdown in 5 minutes. $CHMSG"
# wall "upssched-cmd: sleeping to give servers time to poweroff"
sleep 120s
# Power off PDU outlets to save power.
logger -t upssched-cmd "UPS on Battery Power. PDU outlets 4-srv-drives, 5-srv, 7-pi and 8-homeassistant power down NOW. $CHMSG $TIMESTAMP"
snmpset ...
snmpset ...
snmpset ...
snmpset ...
# wall "End upssched-cmd $1"
;;
onbatt5)
# Shut down servers
logger -t upssched-cmd "UPS on Battery Power. PDU outlets 3-switch and 8-homeassistant power down NOW. $CHMSG $TIMESTAMP"
snmpset ...
snmpset ...
# wall "End upssched-cmd $1"
;;
onlinenotify)
# Log the notification.
logger -t upssched-cmd "UPS back on Line Power. Bringing up network in 3 minutes, servers in 10 minutes. $CHMSG $TIMESTAMP"
# wall "End upssched-cmd $1"
;;
online3)
# Power on PDU outlets for main switch to prep for server startup.
logger -t upssched-cmd "UPS back on Line Power. Bringing up PDU outlet 3-switch NOW. $CHMSG $TIMESTAMP"
snmpset ...
# wall "End upssched-cmd $1"
;;
online10)
# Power on PDU outlets for servers now.
logger -t upssched-cmd "UPS on Line Power. Bringing up PDU outlets 5-srv, 7-pi, 8-homeassistant NOW. $CHMSG $TIMESTAMP"
snmpset ...
snmpset ...
snmpset ...
# wall "End upssched-cmd $1"
;;
upsgone)
logger -t upssched-cmd "UPS communication has been gone awhile on $HOST. $TIMESTAMP"
;;
)
logger -t upssched-cmd "Unrecognized command: $1"
;;
esac
NUT.CONF
MODE=netclient
UPS.CONF
maxretry = 3
UPSD.CONF
# empty
UPSD.USERS
# empty
UPSMON.CONF
RUN_AS_USER nut
MONITOR ups@192.168.0.77 1 upspi <pw> slave
NOTIFYCMD /usr/sbin/upssched
SHUTDOWNCMD "sudo /sbin/shutdown -P +0"
NOTIFYMSG ONLINE "UPS %s on line power"
NOTIFYMSG ONBATT "UPS %s on battery"
NOTIFYMSG LOWBATT "UPS %s battery is low"
NOTIFYMSG FSD "UPS %s: forced shutdown in progress"
NOTIFYMSG COMMOK "Communications with UPS %s established"
NOTIFYMSG COMMBAD "Communications with UPS %s lost"
NOTIFYMSG SHUTDOWN "Auto logout and shutdown proceeding"
NOTIFYMSG REPLBATT "UPS %s battery needs to be replaced"
NOTIFYMSG NOCOMM "UPS %s is unavailable"
NOTIFYMSG NOPARENT "upsmon parent process died - shutdown impossible"
NOTIFYFLAG ONLINE WALL+EXEC+SYSLOG
#+SYSLOG+WALL
NOTIFYFLAG ONBATT WALL+EXEC+SYSLOG
#+SYSLOG+WALL
NOTIFYFLAG LOWBATT SYSLOG+WALL
NOTIFYFLAG FSD SYSLOG+WALL
NOTIFYFLAG COMMOK SYSLOG+WALL
NOTIFYFLAG COMMBAD SYSLOG+WALL
NOTIFYFLAG SHUTDOWN SYSLOG+WALL
NOTIFYFLAG REPLBATT SYSLOG+WALL
NOTIFYFLAG NOCOMM SYSLOG+WALL
NOTIFYFLAG NOPARENT SYSLOG+WALL
MINSUPPLIES 1
POLLFREQ 10
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME 15
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 5
UPSSCHED.CONF
CMDSCRIPT /etc/nut/upssched-cmd
PIPEFN /run/nut/upssched.pipe
LOCKFN /run/nut/upssched.lock
AT ONBATT ups@192.168.0.77 EXECUTE onbattnotify
AT ONBATT ups@192.168.0.77 START-TIMER onbatt30s 30
# Disabled the online cancel actions in favor of having certainty on the state.
# Servers will go down on an OB event, but that's fine. When Nutpi sees it back
# OL it will bring up the servers
#AT ONLINE ups@192.168.0.77 CANCEL-TIMER onbatt30s
#AT ONLINE ups@192.168.0.77 EXECUTE onlinenotify
UPSSCHED-CMD
#! /bin/sh
#
# This script should be called by upssched via the CMDSCRIPT directive.
#
# The first argument passed to your CMDSCRIPT is the name of the timer
# from your AT lines.
logger -i -t upssched-cmd "Calling upssched-cmd $1"
UPS="ups@192.168.0.77"
HOST=$( uname -n)
STATUS=$( upsc $UPS ups.status 2>&1 | grep -v '^Init SSL' )
CHARGE=$( upsc $UPS battery.charge 2>&1 | grep -v '^Init SSL' )
CHMSG="$UPS[$STATUS]:$CHARGE%"
case $1 in
onbattnotify)
# Log the Notification.
logger -t upssched-cmd "UPS on Battery Power. Shutting down $HOST in 30 seconds. $CHMSG"
wall "upssched-cmd: UPS on Battery Power. Shutting down $HOST in 30 seconds. $CHMSG"
;;
onbatt30s)
# Shut down servers
logger -t upssched-cmd "UPS on Battery Power. $HOST shutting down NOW. $CHMSG"
wall "upssched-cmd: UPS on Battery Power. $HOST shutting down NOW. $CHMSG"
sudo shutdown -P +0
;;
# onlinenotify)
# # Log the notification.
# logger -t upssched-cmd "UPS back on Line Power. $HOST is already online. $CHMSG"
# wall "upssched-cmd: UPS back on Line Power. $HOST is already online. $CHMSG"
# ;;
upsgone)
logger -t upssched-cmd "UPS communication has been gone awhile on $HOST."
;;
*)
logger -t upssched-cmd "Unrecognized command: $1"
;;
esac
A basic NUT configuration does an immediate shutdown as soon as an ONBATT status is reached (upssched.conf has “at ONBATT execute…”, which causes the upssched-cmd to run the shutdown command immediately). But you can change that to a timer, which can be cancelled if the UPS goes back online, or only shutdown at LOWBATT.
It’s complicated, but NUT should be able to do everything you have stated as a goal. But it takes some testing.
One thing I found helpful while setting it up is the Dummy UPS driver that is included in the documentation. Rather than plug and unplug a physical UPS during testing you can make text files with various ups statuses and cp one to the dummy’s input file target to make it change to battery power or back online. Use logger to log information into the system journal from upssched-cmd to see what’s running in your script (with a unique keyword to grep on). Monitor in another terminal with journalctl -f | grep yourkeyword to view your messages. This made it much easier to get the upssched stuff sorted out.
One of my goals was unattended power-on management for when I was away from home. If power returned for an amount of time, send power commands to various smart outlets to bring everything back up in sequence. So I used a pretty big upssched-cmd, with timers for both shutdown and power up and different UPS battery levels (no power up until 30% battery, for example). It would have been pretty difficult to debug without the dummy UPS.
Anyway, NUT is really powerful.


It seems like his hand is perfectly positioned to smack her in the face when her foot finds nothing but water and she tips forward.

Apparently this is caused by a wet iron-rich site. The phosphate in bones/teeth/tusks combines with iron to form vivianite. Some varieties of the mineral turn blue when exposed to light. So the fossil finder watches it turn a shade of deep blue. Cool.


There were a lot of the smaller bungalow models of these in a neighborhood I used to live in. Still looking good after 100 years. Not bad for a flatpack house on a truck!


This is what I thought of too. I worked in a building with a warm door handle. Its latch was open during the day, but locked after hours. I assumed the electro-mechanical mechanism generated heat keeping it unlocked.


Cool. It might vary by product. This store lists this particular product as made in Germany, but I don’t know the store. https://www.chroonoo.com/p/stalux-stainless-steel-watch-band-multiple-ends-18-20-22-mm-silver/
Edit: duh, I didn’t notice you linked to that store already.


You might look for Stalux watch bands. Made in Germany and there are some near your budget.
Are we still doing phrasing??

Interesting. Eggs a l’Argenteuil or Oeufs Argenteuil seem to be scrambled egg with asparagus tips. Argenteuil in France is or was known for it’s asparagus. This dish seems to have been in Escoffier’s big book of French cooking from early in the 20th century.
Unfortunately that means a limited sole life and no ability to re-sole. I still tried to like 'em, but I got a pair that had one whole side of the vamp stitched on with no inside thread. Just empty loops of the outside thread interlocking with nothing.
Replacement pair was murder on my pinky toes. Narrower in the toe box than Docs, with a significant ridge from the glued on welt.
I ended up giving them away.
Jim Green boots are a good option, particularly for wide toe box in some of their lasts. No shops for trying on though. But they are made with quality leather, and they contribute to a good cause.
Their boots are made with stitch-down construction, which can be resoled by any cobbler.


PS: rice can go bad in a way that does not smell or look like anything, it continues being white.
Fun fact - the bacteria commonly associated with food poisoning from rice (bacillus cereus) produces several toxins that make you sick. And those toxins are heat stable. So rice that was at an unsafe temperature for hours is not safe to eat even if you reheat to a “safe temperature”. It can still make you sick.
Botulism is similar in this regard. 🌈⭐


I appreciate the jaunty angle of the toilet cistern. It has seen some shit but maintains an indefatigable elan.


Dang it. Well it’s at least where I wanted to throw an HP laptop years ago. Piece of shit. Right into the emergency reset hole.
I agree with you about the sd cards. But pi 4 and higher can boot directly from SSD (in a usb enclosure, or for pi 5 via pci-e add on card). It takes a lot of the pain out of hosting on pi. I also still have an old pi 3b chugging along as a NUT server running off an sd-card with a read-only file system - another solution for the card rot problem.
And they are still lower power then anything x86. For me a mix of both pi and mini-pc work great.