I am using macOS 10.14.6 and docker info shows me that the docker daemon is not running. How do I start the docker daemon from terminal? I have not found any information on doing so anywhere. On Linux you do something like sudo service docker stop, but this is incompatible with MacOS.

I have my own running daemon application that listens to a network port and executes some different commands based on the coming request. All is working fine except when trying to execute the following codesign command. sudo codesign --force --timestamp --options=runtime --entitlements --sign Where I see an error saying errSecInternalComponent. However, when I take the same command and paste it into the terminal it works. I have my application certificate installed under both login and System keychains and set to be Always Trust in settings. I tried adding --keychain option to specify the keychain path for the codesign command. Also, I made sure that both login and System keychains are unlocked during command execution. Besides, I tried adding the following key/value pair to my daemon plist file and restarting it.

SessionCreate

All of the above trials failed to fix the issue, I'm out of ideas and any help would be highly appreciated.

2018 Mac mini previously running Ventura. 32 GB of RAM, 1 TB SSD with plenty of space. Lots of 3rd party apps but not many menubar items or sketchy type software. A pretty clean system. So ever since upgrading to Sequioa, heres what happens: Upon boot, everything is fine for about a day. Then SystemUIServer combined with configd start using 100% of the CPU (out of 600% total). Over the next day or two, it gets worse and worse. You get these little one second beachballs while you're typing. One second goes to two, goes to three. The fan in the mini is spinning annoyingly loudly. After a few days, the system is unusable, so I reboot and everything is fine. For a day. I posted this to the Apple forum but the only suggest was to wipe the system and start over from scratch, which is total nonsense. Things I have tried so far: I've gone through all of my launchd items and deleted all of the ones from old software or from software I don't need. Some had to stay of course, Photoshop won't run without it. I quit the two 3rd party items I had in my menubar. I had a hunch maybe it was a Malwarebytes problem, so I uninstalled it entirely. All this, but no change. The classic next troubleshooting steps to take are to create a new user on this system and see if it happens there, and to install Sequoia on a USB SSD through this machine and see if it happens there. The problem is that 1 day delay before the problem pops up makes it really hard to do that kind of troubleshooting. This isn't (just) a recreational machine, I have work to do. Lots of it. All the time. In the meantime I've just been rebooting every 2 to 3 days and I guess I'm stuck doing that for the foreseeable future. There are two factors that make my setup a little unique. I say a little, because zero 3rd party software is involved, it's all Apple. But this 2018 Mac mini does have 3 monitors installed. And I do have 7 virtual desktop sets setup. So I have 21 total virtual displays with a bunch of windows open on each. But I don't have THAT many windows open on each. I'm not hoarding windows like a Chrome user hoards tabs. I just have areas where I do different kinds of work. Like one for video editing that will have a couple of Finder windows plus iMovie open - but only while I'm working on a video. Another space might have two terminal windows and two browser windows. Nothing dramatic. I tell you this only to suggest that I don't think this problem is related to my "Spaces" or my monitors. Especially since it was like this in Ventura and previous macOS versions for years and while this setup does have some problems, it doesn't have anything quite like this. One more thing: it's not a constant thing once it starts happening, but it happens more and more the longer the Mac runs until it becomes almost constant. BUT I've noticed it tends to be happening a lot when I sit down at my desk and my computer's displays are asleep. I can hear the fan in the mini spinning while it should be idle, so I know the two processes are going nuts. And sure enough, they are. It's as if I have a high CPU screen saver that's also running after the displays go to sleep. But I double checked the screen saver settings and that is not the case. So maybe someone out there has some specific ideas of what might be causing this? Maybe someone knows what would cause configd and SystemIUServer to freak out together in perfect sync? Then pause for a while together, then start up again together?

When running netstat I noticed the suspicious name blackjack. I wonder if it's malware.

PROMPT> netstat -v
Active Internet connections
Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)     rhiwat shiwat    pid   epid  state    options
tcp6       0      0  nameofmachine.local.blackjack fe80::c55b:ddf6:.13569 ESTABLISHED 131072 131072    476      0 0x0102 0x00000204
tcp6       0      0  nameofmachine.local.1024      fe80::c55b:ddf6:.1024  ESTABLISHED 131072 131072    476      0 0x0102 0x00000204

Looking up the pid 476

PROMPT> ps ax | grep 476
476   ??  S      0:19.94 /System/Library/PrivateFrameworks/IDS.framework/identityservicesd.app/Contents/MacOS/identityservicesd

So the process that owns the address seems to be identityservicesd.app, which is an Apple process. This is where my trail ends. There are other mentions of .blackjack occurring on macOS, see [this unanswered Reddit question](https://www.reddit.com/r/HomeNetworking/comments/cmj92b/blackjack_when_running_netstat/) . ### Question: What is it? Malware?

I would like to make periodic backups using rsnapshot on my MacBook. However, as it is a laptop, it will only be powered on at random times. Thus, scheduled tasks might be missed while it is powered off. A solution for this would be anacron which does not seem to be available on macOS though. Apparently macOS' native launchd service is not capable of scheduling jobs in the manner of anacron. Here it says: > If you schedule a launchd job by setting the StartCalendarInterval key > and the computer is asleep when the job should have run, your job will > run when the computer wakes up. However, if the machine is off when > the job should have run, the job does not execute until the next > designated time occurs. All other launchd jobs are skipped when the > computer is turned off or asleep; they will not run until the next > designated time occurs. If my monthly rsnapshot backup is, for example, scheduled for the first day of every month but the laptop is powered off that day, that would mean I lack that backup and only get the next one a whole month later. Is there any workaround to this? Perhaps linking the launchd schedule with some conditional commands in a bash script? The only idea I had to solve this was to schedule the launchd job for every single day at a specific time and execute a script which: 1. Checks a timestamp log file if a successful backup has run this month 2. If yes --> exit, if no --> run backup 3. If backup successful --> add timestamp to that file Though that seems unnecessarily complex in comparison to anacron jobs that you can create on Unix systems.

Just installed Ventura on a 2017 macbook pro 15", and for the last 10 minutes or so a daemon called knowledgeconstructiond has been using sizeable but not problematic amounts of CPU. Was curious what it was (intriguing name) and didn't get far with a google search (found this: https://keith.github.io/xcode-man-pages/knowledgeconstructiond.8.html) . What is knowledgeconstructiond doing?

I've just updated to the latest MacOS 10.13.2 and after restarting, my machine asked me to allow incoming network connections for "rapportd". After blocking it and checking in the firewall config, I can see that this is an executable in /usr/libexec/rapportd which was created on my machine on the 1st of December. That's a day after I installed the security update 2017-001 (for the second time; autoupdate didn't seem to notice that I'd manually updated it), and I haven't installed or updated any other software recently / around that time. Google Chrome updates whenever it feels like it, so this could be related to a Chrome update (no idea when it last updated). The internet suggests this is related to some banking protection program but that doesn't seem to fit here, and from a vague text-edit inspection of the binary I can see that it references /System/Library/PrivateFrameworks/Rapport.framework/Versions/A/Rapport (a framework created on my machine back in July and updated in October) which makes me think this is likely to be a new 1st-party OS daemon. --- What does rapportd do?

For the past couple of weeks, a process identified as usernoted appeared to "take over" my machine after a few hours of use, eating over 99% of available CPU. Force quitting the process doesn't help; only a system restart puts usernoted to sleep for a while. What is this process and how do I get it under control? I am running **OS X 10.10.5** (build 14F1021).

I have made a few Mac daemons in the past. They either run at launch or run at a specific time interval, for example, once every hour. I would like to know if it's possible to run a program on an event. Particularly, I would like the script to be executed when a specific file on the hard drive is edited. Looking up the guides on launchd, I can't find any mention of anything like this. I'm guessing I just don't know the right wording for what this is called. Or perhaps this isn't possible? Could anyone please give me some pointers as to how to get started with something like this?

I'm having trouble creating a successful daemon. Before PostgreSQL went to naming their folders with an @ symbol, I had a working daemon, but now something, somewhere has changed that I can't figure out. If I run: sudo -u _systemuser /opt/homebrew/opt/postgresql@14/bin/postgres -D /opt/homebrew/var/postgresql@14 PostgreSQL starts fine. However this plist doesn't work: Label homebrew.mxcl.postgresql RunAtLoad GroupName _systemuser UserName _systemuser ProgramArguments /opt/homebrew/bin/postgres -D /opt/homebrew/var/postgres In LaunchControl, it says "This job has failed for no apparent reason." So if I enable logging: Label homebrew.mxcl.postgresql14 RunAtLoad GroupName _systemuser UserName _systemuser ProgramArguments /opt/homebrew/opt/postgresql@14/bin/postgres -D /opt/homebrew/var/postgres@14 StandardErrorPath /opt/homebrew/var/log/postgresql@14.log StandardOutPath /opt/homebrew/var/log/postgresql@14.log I get the error "User _systemuser cannot write to the file: "file:///opt/homebrew/var/log/postgresql@14.log"" I've changed the permissions to those folders with: sudo chown -R _systemuser /opt/homebrew/var/postgresql@14 sudo chgrp -R _systemuser /opt/homebrew/var/postgresql@14 However, using this logging plist does evoke a new error in LaunchControl: 2024-12-26 11:06:02.649106 Service could not initialize: posix_spawn(/opt/homebrew/opt/postgresql@14/bin/postgres), error 0xd - Permission denied But as I said at the start, PostgreSQL starts up fine from CLI. Stumped. Any ideas on what might be the problem?

I have installed Jomo on my Mac, located at /Applications/Jomo.app, and I want it to start automatically when I log into my account. I want to create a script to make it run once I log in, without being able to change this from the Settings App. The problem is that I’ve created a launchd LaunchDaemon to execute the program. I want the program to be executed from an administrator account (with root permissions) so that it runs for a normal user account. However, the keepalive setting is causing it to restart every 4 seconds, which is very annoying. I want it to run just once when I log in and not restart repeatedly. Here’s the .plist file I created for launching the program with keepalive: Label com.jomo.start ProgramArguments /Applications/Jomo.app/Contents/MacOS/Jomo RunAtLoad KeepAlive WorkingDirectory /Applications/Jomo.app/Contents/MacOS Could anyone help me modify the keepalive settings so that Jomo starts only once at login and prevent it from restarting repeatedly? Thank you!

man locate.updatedb says that the database for locate is updated weekly. That is confirmed by /System/Library/LaunchDaemons/com.apple.locate.plist, which has Weekday 6 To run nightly instead of only on that weekday, as root I tried to remove that part: plutil -remove StartCalendarInterval.Weekday /System/Library/LaunchDaemons/com.apple.locate.plist But that failed, "Operation not permitted," with no further explanation. How can I cause updatedb to run nightly? Sequoia 15.0.1, macbook pro, M3 pro.

I’ve been trying to change the root password via Terminal on macOS. I launched Terminal by holding cmd + S while booting, which logged me automatically in as root without password. When I type in Passwd root or Passwd and then hit enter, I just get an error message that says > the daemon encountered an error processing request two times in a row. If a log into my user and then try that it works perfectly but I want to change it from the “cmd+S” menu.

One or another of the various macOS background daemons that comes with the operating system is always popping up and using a ton of CPU in the background. This is generally slightly bothersome, but it's *really* annoying while I'm trying to play demanding video games that really need the system's full attention. This visibly hurts the framerate and I need to go and investigate in iStat Menus or something to nuke the offending process manually. Is there a way to comprehensively pause or at least aggressively throttle *all* system background activity while I'm doing something demanding? Mostly I want this for applications that are demanding of input responsiveness, like video games, but it would be nice for CPU intensive batch jobs that might take an hour or two to run, too; tell the system to please chill out in the background and not suck up either CPU or I/O to let the jobs run either more repsonsively or faster. I'm being non-specific because “Why is daemon X taking up so much CPU” is a common genre of question on this site and others like it (previously , previously , previously , previously , previously , previously , previously , previously , previously , previously , previously ). *All* of these daemons are implicated at various points. Probably the worst offenders are syspolicyd, AMPDevicesAgent, and worst of all suggestd, but all the usual suspects show up at one point or another. As such, I'm not looking for a *permanent* answer for how to fix these problems all the time, i.e. how to make these daemons go away, because: 1. There's too many of them; I am resigned to just having weird energy leaks and performance problems until Apple provides some more transparency for their background daemons. 2. At least for right now, they're *mostly* behaving themselves *most* of the time, and I realize they provide value by indexing things and doing stuff in the background to provide responsiveness in the moment. 3. With an Apple Silicon machine, they appear to mostly be persistently scheduled onto the Efficiency cores and have less of a devastating performance and battery impact than they used to, as a result. What I'm looking for is more of a *temporary* fix for when I need maximum performance, which would allow me to simply quiet down the background performance interference rather than shutting it down completely. I know the system needs this stuff to run for all the functionality to work and I don't want to take an axe to necessary parts of the OS, but I'd also like to get a consistent 120 FPS in 5-year-old games without dropping to 2-3FPS for a minute and getting killed because it was *really* important to Mail.app to make sure I could instantly search for some direct marketer's phone number because it downloaded a new message into its spam folder.

I want to get rid of some system services completely. I turned off sip with csrutil disable. Then following command sudo launchctl disable com.apple.cloudphotod Gave me an unexpected answer: Unrecognized target specifier, did you mean gui/501/com.apple.cloudphotod I've read man, searched forums and so on. But I can't get why do I need specify the context agent is running in, how do I know that from launchctl list and is the a way to avoid the need to specify it? There are many services and I'm completely uncertain which one is in which context. Side question: I also was looking for a gui tool such as Windows Services.msc, found Soma-zone's LaunchControl. Downloaded tar.gz archive, unarchived, started the app, and... it says "can't open the app". Did I miss something and tar.gz needs some special handling? Never dealt with that.

My script to mount an S3 bucket works fine, but mount at boot is not working. I tried launch daemons on macOS Sonoma, compiling with this plist. Here is the code:

Label
	local.hfs34
	ProgramArguments
	
		sshfs
		ubuntu@51.21.105.210:/
		/users/oscarristolfi/red34
		-o IdentityFile="/Users/oscarristolfi/.ssh/redchiavissh.pem"
		-o reconnect,allow_other,volname=hfs-red2
	
	RunAtLoad

This is an improvement to previously discussed: https://apple.stackexchange.com/questions/468042 I used to love Automator for such tasks, but found in this task passing arguments with filenames in Automator steps failing for me. I'm open to good script as well. I have an Intel and M2 Macs, old one is portable and I found M2 is recoding (lower res and crop) video faster than Intel would even with sending results over WiFi. Puzzling myself to do following 1. Samba share on M2 accessible over WiFi 2. Either edit (if was emptied in step 4) or new file queue.txt with YouTube link. Folder MMi is needed in step 4 for correct work 3. A nifty programs entr and yt-dlp looking at updates in queue.txt and if there is new - downloading 720p .webm video as example https://www.youtube.com/watch?v=WO2b03Zdu4Q

ls queue.txt | entr yt-dlp -q -f "best[height yt.txt
        ' _ {} \;
    done

5. As it's finished, need to rsync it back to Intel Mac over WiFi (ssh keys are already exchanged)

rsync MMi/*.mp4 user@intel_mac/MMi

Is there a way to combine everything in one script, other than maintaining three "daemon", maybe launchctl on a .plist or python program? Are there guides or templates to get this script running as a daemon on macOS?

Companies like Google and others love to install daemons/services on ~/Library/LaunchDaemons Sonoma alerts me when this happens, but I want to be able to prevent bloat services like this even installing. Unfortunately, I create things for the web and I need to test it using Chrome. Every time I run chrome, here we go, it fiddles with the LaunchDaemons and adds its crap. I have thought of creating a zero byte file there, with the name they expect but with permission 000 (chmod 000), but because sometimes you are installing apps that have my admin password, these files will be overwritten. I know that some files in the system have permissions that not even with a superuser permission one can access. How can I set these files like that, so they cannot be overwritten?

I have an 14" M1 Max that gets very poor battery life, which I suspect is mainly due to the installed internet filter, Qustodio, causing high CPU usage from opendirectoryd. As per activity monitor, opendirectoryd is constantly using ~20% CPU, but can spike to 40. There is a very causal relationship between opendirectoryd usage and Qustodio. If Qustodio is uninstalled, the usage disappears, and there is an instant spike in usage the moment Qustodio is reinstalled. Opening the console, I see no error messages relating either to opendirectoryd or to Qustodio. Unfortunately, that is as far as I was able to figure out on my own. I don't know why Qustodio is causing such high opendirectoryd usage, nor do I know how to fix it. **What should I do to investigate further, and what can possibly be done do fix it?** Thank you.

I have the following shell script:

#!/bin/bash
time=$(time);
imagesnap -q "/var/captures/$time.jpg";

When I run it in the terminal, everything works. But when I run it using launchtl or crontab at login, nothing happens. Does anyone know how to run this script at login? It it even possible? Thanks for any answers in advance! ## Note The issue is not with crontab or launchctl, I have got them to work. They just wont work with the camera. I am using [Imagesnap](https://formulae.brew.sh/formula/imagesnap#default) as a dependency for capturing images. ## My Machine I am using macOS 14.1 Beta 2 on a 2021 macBook Pro