The “sweep” daemon job that I developed in Is there a simple approach to robotically schedule a transfer of recordsdata matching a sure sample from a consumer listing to a USB drive? and What went fallacious with my launchd plist? appears to be working simply high quality. The final time it truly had recordsdata to switch to the exterior drives was yesterday morning; this morning, it had no precise work to do, so I do not know whether or not it ran or not.
This morning, I created one other launchd plist (“backlocal,” which backs up a few rarely-changed Samba shares each six months), and I did a launchd load on it simply now, adopted by a launchd record, to confirm that it was loaded.
“backlocal” was certainly within the launchd record, however “sweep” was not (I instantly did a launchd load to manually reload it).
I do not know whether or not it ran this morning or not. All I do know is that if I carry up the console, and search “all messages” for “sweep,” I get:
5/20/23 8:00:09.787 AM com.apple.xpc.launchd[1]: (sweep[3314]) Service exited with irregular code: 1
5/21/23 8:00:05.558 AM com.apple.xpc.launchd[1]: (sweep[3573]) Service exited with irregular code: 1
5/22/23 8:00:05.744 AM com.apple.xpc.launchd[1]: (sweep[3828]) Service exited with irregular code: 1
5/23/23 8:00:15.388 AM com.apple.xpc.launchd[1]: (sweep[590]) Service exited with irregular code: 1
I took a have a look at a few threads that got here up robotically after I entered the above log messages, What does “Service exited with irregular code: 1” imply? and launchd notification on irregular exit however I am undecided if they’ve any bearing right here.
Might these messages have one thing to do with my not seeing “sweep” in launchd load? I’ll word that “sweep” did efficiently sweep a file to the exterior backup drives on the twenty third. I may also word that the latest reboot was about Midday on Monday.
