Re: Why MacOS is not a "fun" Unix to work with

On 12/14/24 9:14 PM, vallor wrote:

# time -p tmutil latestbackup
tmutil: latestbackup requires Full Disk Access privileges.
To allow this operation, select Full Disk Access in the Privacy
tab of the Security & Privacy preference pane, and add Terminal
to the list of applications which are allowed Full Disk Access.
real 59.67
user 0.00
sys 0.00
  _ _ _ _ _ _ _
 So it takes almost a full minute to give an "access denied"?

Something's wrong with your system; just a few seconds req'd:
Same error my first time too (& just a few seconds to respond):
admin$ time -p tmutil latestbackup
tmutil: latestbackup requires Full Disk Access privileges.
To allow this operation, select Full Disk Access in the Privacy
tab of the Security & Privacy preference pane, and add Terminal
to the list of applications which are allowed Full Disk Access.
real 0.05
user 0.00
sys 0.00

Also, I already added Terminal to the list.  MacOS wants something else.

One does have to relaunch Terminal, as the instructions say:
admin$ time -p tmutil latestbackup
/Volumes/.timemachine/5C733EB8-AEBA-483A-A71C-DCB2E40562FD/2024-12-14-211509.backup/2024-12-14-211509.backup
real 0.36
user 0.00
sys 0.01

I can run the command from the Terminal on the console, but not via ssh. In the "Full Disk Access" application list, there's a "+" to add another
application.  Clicking that gives a file dialog, but there is no way
to point it at /usr/sbin/sshd.

Seems that that's a deliberate choice.

Linux wouldn't do this to me.

Of course it wouldn't.

To check Time Machine status, I have to vnc in to the console -- where the
frame rate at login goes into the dirt, because Sequoia has a lovely moving
background on the login screen.
 Honestly, I don't think these kids can steer...

Or just sit at the physical machine like most folks do.  From there, {Finder/System Settings/General/Time Machine} gets you to the data of the last backups to each attached TM target, plus also the first.
-hh