I am currently running a script that is backing up files from my work machine to a backup machine.

As soon as the backup is completed I would like the script to power off the backup machine before powering itself off.

Is that simple? I am not going to experiment now as it well past my bedtime.

'night. Alan

--
sed (GNU sed) 4.8
Packaged by Debian
Copyright © 2020 Free Software Foundation, Inc.
Licence GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Jay Fenlason, Tom Lord, Ken Pizzini,
Paolo Bonzini, Jim Meyering, and Assaf Gordon.

This sed program was built with SELinux support.
SELinux is disabled on this system.

GNU sed home page: <https://www.gnu.org/software/sed/>.
General help using GNU software: <https://www.gnu.org/gethelp/>.
E-mail bug reports to: <bug-sed@gnu.org>.

On 6/1/2023 6:33 PM, pinnerite wrote:
> I am currently running a script that is backing up files from my work machine to a backup machine.
>
> As soon as the backup is completed I would like the script to power off the backup machine before powering itself off.
>
> Is that simple? I am not going to experiment now as it well past my bedtime.
>
> 'night. Alan

As a noob, my advice is to test the shell response
to the command, while sitting in front of the machine.
You would be surprised, how many situations it just
does not work properly. It is better to debug this
while next to the machine, than repeatedly whacking at
it in desperation, remotely.

If you were using a systemd runlevel hack, that might
make a difference to the response of the usual command,
as well. Maybe using single user runlevel is different than
multiuser (traditional runlevels have integer numbers
identifying them, systemd has labels of some sort).

So the idea is, when you're absolutely satisfied the
command is working right, while sitting in front of it,
only then do you drive off into the sunset, and test the
exact same thing through being secure-shelled in.

https://www.debian.org/releases/buster/amd64/ch08s01.en.html

poweroff # administration commands need elevation
shutdown -h now
systemctl reboot
systemctl poweroff

The descriptions always start with a confident tone... until you try them :-/

My first experience doing something stupid, was in uni, and
loading the "empty workspace" in APL, after normal hours. Nothing
really worked in there (quelle suprise). So I figured, "OK, time
to go home". I turned off the power to the teletype, waited,
then turned it on, and my session... was still active. Now what
to do. Hmmmm. To fix that, required walking over to the computer
center, and getting the operator to kick me off. But, you're also leaving
the terminal open, during the walk across campus. Before trying this,
I should have used a terminal across from the operators position, so the
"walk of shame" would be shorter :-) And this is why we're careful
with the traps we dig and fall into. Test that the basics work first.

Paul