Allan

Gotcha. Sometimes I can really dense and miss the bigger picture.

can you clarify?

@bmike - forgive my ignorance here...

@bmike….

Just out of sheer (morbid) curiosity...what exactly do these spammers get from this?

I missed this the first time around. Thanks for pointing it out. This is truly weird.

As for duplicating a drive, you can try dd. Example command: dd if=/dev/diskX of=/dev/diskY bs=1M

@agarza, In the meantime I tested a network Time Machine setup with my iMac (Catalina) and a Synology NAS. It had no problem functioning as expected. I am beginning to think there’s an issue with Sonoma.

Roger that

Sounds good.

True, but I am always hesitant to mess around with good data.

It’s like priming the pump, so to speak. The device’s UUIDs will be known so it shouldn’t have to redectect the volume

There are days I resent this upgrade all the time model vendors use. Just reading on MacObserver How TM broke on Sonoma. I’m thinking you create and execute a TM backup locally first, then move it to the network.

BRB

This is Sonoma, right?

Go Apple menu > System Settings > General, then click Time Machine. If you see the share over SMB, you should see it here

Sorry…. Was checking on something

In the question, you said you were using MBR. Can you reformat with GPT. the Apple Support document mentioned that MBR could fail to see the partitions

Use the USB flash for now so you can reformat quickly. Make sure you’re using APFS and GPT (MBR can be flaky)

Try sharing from a Windows machine first. Let’s see where that goes

You wouldn’t happen to have a) that USB flash to test with again, or b) a Windows (or Linux) computer you can use to test with? The idea is to narrow the issue down to the Mac or to the router

Also see this Apple Support document for the types of formats supported.

Did you enable Time Machine Support on the router’s settings? See the user manual for details

Upgrade to Ventura. Monetrey had an issue of being too locked down and you’d get security notifications like this. Don’t overcomplicate matters

That screen is a privacy and security (one time) question whether you want mediasharingd, a totally different daemon from the one you’re tinkering with, to have network access. There’s no need to unload any plist as there’s no problem. Just allow network access as its a legit and safe process.

They are environment variables. The fist one is which display things are rendered and the second defines the temp sockets it will listen on

sharingd does not create “weird window popups;”. You also didn’t show which sockets it was bound to…you provided environment variables. To be candid, the whole post is rife with syntactical errors (not grammar, but usage) that indicates you’re quite new at this. Before tinkering with daemons, boot into Safe Mode (diagnostics mode) and see if you still get the problem. Also create a temp user, login to that account and see if the popup remains. Let’s start there

Please edit your post with a clear description of the issue and why you think unloading a plist will solve it.

Nobody said it wasn’t happening nor was it not legitimate. I just said we should look at the underlying cause it because it didn’t sound correct. I am here mostly to assist folks, but I tend to go elsewhere when the tension levels up for no reason. I wish you the best.

“My desktop Macs” = “computer lab”. Making this personal isn’t productive.

As for your command, I think you can achieve what you want with nohup {sleep 10; shutdown -h now};exit. That should push the compound (grouped in braces) command into the background and detatch it from the current user (allowing it to run in background while Terminal closes) then the clean exit will occur achieving your result. (Not tested)

I shutdown/reboot my desktop Macs all the time via CLI and don’t experience a reopen of the windows nor a hangup on the new login session. Maybe we should look at that issue because what you’re experiencing doesn’t sound correct.

I’ve been reading the comments and the part I don’t understand is why you need an exit code for terminal when the system is being shutdown. Why is it critical that you get a clean exit code here?

Then I wish you the best in obtaining your answer. I’m certain you’ll be able to juggernaut your way through to one

The problem here is you are not recognizing that the question you’re asking is “I want a good boat and I don’t know the type of weather.” That said, you’re comment is not at all constructive here

Yes, asking to set up a “good” anything is opinionated because what defines good but our opinions. Metadata is essentially freeform; you use it to describe your data. We aren’t process consultants here. You need to define your parameters and creat your metadata structure accordingly

Ostensibly it refers to macOS, but the question is much broader in scope - this is as you describe “a best practice for applying meta data.” macOS as with other modern OSes, all have meta data capabilities. A better question would be to find a best practice that works for you and then how to implement it in macOS (if not readily apparent). We can’t tell you what that broadly defined best practice could/would be.

I’m voting to close this question because as written it’s not about Apple hardware, software, or services as defined in the Help center.

I’ll have to research this a bit more. On mine, it just works (not trying to be flippant). I have no need to boot an external volume, but when I tried this, it worked.

How are you booting into Recovery? Just Opt-R, correct?

Recovery won’t have a login prompt. That’s by design

Is your an account an admin?

No. Recovery is just for that…recovery. It has only the basics. To boot and get the start up options, turn off the press and hold the power button until you see the options menu. See support.apple.com/en-us/HT201255

You don’t do that in Recovery. You have to hold the power button until you get start up options

Recovery is not the sane boot image as your regular macOS. When it starts, there are no accounts, just root and it’s already signed in. What are you trying to do?

ifconfig -a should print out every network interface

ifconfig -a | grep inet

Do ifconfig -a

Then try en1

I’m doing this from memory