Removing com.apple.ifdreader with launchctl

If I do for example (on Mac):

launchctl remove com.apple.ifdreader
launchctl stop com.apple.ifdreader


Will I remove the driver from the cache or from the disk?

After a restart the com.apple.ifdreader driver will be enable again?

MacBook Pro 13″

Posted on Sep 15, 2023 9:33 AM

Reply
Question marked as Top-ranking reply

Posted on Sep 15, 2023 12:10 PM

Hi there...



TL;DR

  • You typically want to use launchctl load -w and launchctl unload -w.
  • start and stop are usually reserved for testing or debugging a job.

Details

  • launchctl start <label>: Starts the job. This is usually reserved just for testing or debugging a particular job.
  • launchctl stop <label>: Stops the job. Opposite of start, and it's possible that the job will immediately restart if the job is configured to stay running.
  • launchctl remove <label>: Removes the job from launchd, but asynchronously. It will not wait for the job to actually stop before returning, so no error handling on this one.
  • launchctl load <path>: Loads and starts the job as long as the job is not "disabled."
  • launchctl unload <path>: Stops and unloads the job. The job will still restart on the next login/reboot.
  • launchctl load -w <path>: Loads and starts the job while also marking the job as "not disabled." The job will restart on the next login/reboot.
  • launchctl unload -w <path>: Stops and unloads and disables the job. The job will NOT restart on the next login/restart.

https://apple.stackexchange.com/questions/29056/launchctl-difference-between-load-and-start-unload-and-stop

1 reply
Question marked as Top-ranking reply

Sep 15, 2023 12:10 PM in response to Maxigame99

Hi there...



TL;DR

  • You typically want to use launchctl load -w and launchctl unload -w.
  • start and stop are usually reserved for testing or debugging a job.

Details

  • launchctl start <label>: Starts the job. This is usually reserved just for testing or debugging a particular job.
  • launchctl stop <label>: Stops the job. Opposite of start, and it's possible that the job will immediately restart if the job is configured to stay running.
  • launchctl remove <label>: Removes the job from launchd, but asynchronously. It will not wait for the job to actually stop before returning, so no error handling on this one.
  • launchctl load <path>: Loads and starts the job as long as the job is not "disabled."
  • launchctl unload <path>: Stops and unloads the job. The job will still restart on the next login/reboot.
  • launchctl load -w <path>: Loads and starts the job while also marking the job as "not disabled." The job will restart on the next login/reboot.
  • launchctl unload -w <path>: Stops and unloads and disables the job. The job will NOT restart on the next login/restart.

https://apple.stackexchange.com/questions/29056/launchctl-difference-between-load-and-start-unload-and-stop

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Removing com.apple.ifdreader with launchctl

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.