Using Universal Control in macOS 12.3 Monterey and iPadOS 15.4

Mouse motion is enough to keep a Mac from going to sleep, but once it does sleep, you need a key-press to wake it.

Fortunately, you can get some very small keyboards. A cheap USB number-pad would probably be enough.

No. Mouse movement alone is not enough, but mouse click (or trackpad tap) works just fine. The idea is that accidentally moving the mouse can easily happen, but button presses are assumed deliberate.

1 Like

On the other hand, a two line shell script is even cheaper:

#!/usr/bin/env bash
ssh <username>@<lan address> "caffeinate -u -t 1 || exit 1;"



I’ll get very confused about which computer the documents I create are filed on. What would be great is if my home directory on the iMac was actually a symbolic link to my home directory on the Studio. Is this possible, and if so, how?

You could share the home directory of the Studio and mount it on the iMac.

Thanks for the suggestion. Is it possible to do this in a way so that when I log in on the iMac, the Desktop I see is the desktop of the Mac Studio (and similarly, the home directory I see is the Mac Studio one, rather than the iMac one)?

It is probably dangerous to share desktops and homes directly.
I suggest is to create a symbolic link within the home of the iMac to the home directory of the mounted disk of the Studio, and a symbolic link within the desktop of the iMac to the desktop directory of the mounted disk of the Studio.
You can automatically mount the Studio home to the iMac by first mounting it by hand, then creating an alias of the mounted home, and put the alias among the login items of the iMac user (from the System Preferences).
On the Studio, you have to share the home folder by adding it in the File Sharing section of the Sharing System Preference.



I would recommend using aliases instead of symbolic links – if the Studio’s share isn’t already mounted, double-clicking the alias will mount it and open the folder. I don’t think a symbolic link will do that.

Apple used to offer a remote home directory feature as part of MacOS X Server, and while it worked reasonably well, there could sometimes be sync errors. However, some years ago they dropped support for this feature in client MacOS (certainly by Mojave, possibly one release prior), so you couldn’t use remote home directories even if connecting to a Server that supported them. Based on this, I would agree with @franconi that it’s a bad idea to try and essentially recreate a system that even Apple didn’t feel they could support satisfactorily.