mac启动自动运行程序_什么启动了，为什么在我的Mac上运行？

mac启动自动运行程序

You’re scrolling through Activity Monitor when you notice a process you’re not familiar with: launchd. Should you be worried? No: this is actually a core part of macOS.

当您发现不熟悉的进程：启动时，便在“活动监视器”中滚动。 你应该担心吗？ 否：这实际上是macOS的核心部分。

This article is part of our ongoing series explaining various processes found in Activity Monitor, like kernel_task, hidd, mdsworker, installd, WindowServer, blued, and many others. Don’t know what those services are? Better start reading!

这篇文章是一部分我们正在进行一系列解释各种进程在活动监视器中发现，像kernel_task ， hidd ， mdsworker ， INSTALLD ， WindowServer ，发蓝，和其他许多人。 不知道这些服务是什么？ 最好开始阅读！

This particular process, launchd, is the service management framework used by macOS, similar in some ways to Service Control Manager on Windows or systemd on many Linux distributions. A “service” is anything running in the background; on macOS these are commonly referred to as daemons and generally have names ending with the letter “d.” Most everything your Mac does—connecting to networks, showing things on the display, and backing up your files—is done by a daemon on some level.

启动的此特定过程是macOS使用的服务管理框架，在某些方面类似于Windows上的Service Control Manager或许多Linux发行版上的systemd。 “服务”是在后台运行的任何内容； 在macOS上，这些通常称为守护程序，并且通常以名称以字母“ d”结尾。 Mac所做的大部分工作-连接网络，在显示屏上显示内容以及备份文件-在某种程度上都由守护程序完成。

When you turn on your Mac, launchd is one of the first things launched, after the kernel. This is why launchd has the Process ID, or PID, of 1, on every Mac system.

当您打开Mac时，启动是继内核之后启动的第一件事。 这就是为什么在每个Mac系统上启动的进程ID或PID为1的原因。

The only lower number is 0, which belongs to the kernel, represented here as kernel_task.

唯一较低的数字是0，它属于内核，在此表示为kernel_task。

After launching, launchd proceeds to to launch all of the other daemons your Mac needs in order to run. After you Mac starts up, launchd continues running in the background to check that daemons are still running, and to launch any daemons needed later to run your various programs.

启动后，launched会启动您的Mac运行所需的所有其他守护程序。 Mac启动后，launchd会继续在后台运行，以检查守护程序是否仍在运行，并启动以后运行各种程序所需的所有守护程序。

It’s very rare for launchd to take up many system resources, and when it does happen, rebooting your Mac is usually enough to fix it. Occasionally a buggy program trying to launch faulty daemons can cause launchd to use up a bunch of CPU. If you’ve installed something recently, try removing that and seeing if it helps.

启动它很少会占用许多系统资源，并且一旦发生，重新启动Mac通常就可以修复它。 有时，有错误的程序试图启动错误的守护程序可能会导致启动程序占用大量CPU。 如果您最近安装了某些东西，请尝试将其删除并查看是否有帮助。

For the most part, launchd isn’t anything users need to think about, but it is possible to interface with it directly thanks to launchctl, a Termianl tool for interfacing with launcd. Type launchctl list and you’ll see a list of every background service currently running on your Mac.

在大多数情况下，launchd并不是用户需要考虑的任何事情，但是得益于launchctl(用于与launcd交互的Termianl工具)，可以直接与它接口。 键入launchctl list ，您将看到Mac上当前正在运行的每个后台服务的列表。

Messing with this much more is not a good idea unless you’re a very advanced user, but anyone interested can type launchctl help for a list of potential subcommands, or reading this advanced launchd tutorial.

除非您是一个非常高级的用户，否则launchctl help很多时间来解决这个问题不是一个好主意，但是有兴趣的任何人都可以键入launchctl help以获得潜在的子命令列表，或者阅读此高级启动的教程。

翻译自: https://www.howtogeek.com/319048/what-is-launchd-and-why-is-it-running-on-my-mac/

mac启动自动运行程序