我正在尝试加载单个用户的 LaunchAgent plist。目录下所有现有的plist文件都拥有用户和用户默认组的权限，
如果我对我的 plist 文件使用这些权限并尝试加载，我会得到
$ sudo launchctl load -w -F $HOME/Library/LaunchAgents/com.ionic.python.ionic-fs-watcher.startup.plist
/Users/timothy/Library/LaunchAgents/com.ionic.python.ionic-fs-watcher.startup.plist: Path had bad ownership/permissions
如果我将权限设置root:wheel为相同的命令有效。
我想我要加载错误的方式，所以我尝试了这个：
sudo launchctl load -D user ~/Library/LaunchAgents/com.ionic.python.ionic-fs-watcher.startup.plist
# Similar result, just lots of `Operation not permitted` instead of `service already loaded`
launchctl load -D user com.ionic.python.ionic-fs-watcher.startup.plist
但是从 100 行的输出来看，它似乎正在尝试加载每个存在的 plist 文件。
该工具的文档似乎表明这只会扫描 plist 文件~/Libraries（见下文），
如何为当前用户加载 LaunchAgent？
$ launchctl help load
Usage: launchctl load <service-path, service-path2, ...>
-w If the service is disabled, it will be enabled. In previous
versions of launchd, being disabled meant that a service was
not loaded. Now, services are always loaded. If a service is
disabled, launchd does not advertise its service endpoints
(sockets, Mach ports, etc.).
-F Forcibly load the service. This flag will ignore the service's
disabled state. In previous versions of launchd, this flag
would also ignore the ownership and permissions of the
specified launchd.plist. This is no longer the case. Note that,
unlike the -w flag, this flag will not modify the service's
disabled state; it will instead only ignore it for the load
operation.
-S <session>
This flag takes a single argument which is the name of a
session and may only be used when loading agents. All daemons
exist within the same session, which is the system session.
Agents may designate which sessions they can be loaded in with
the LimitLoadToSessionType key.
-D <domain>
Loads launchd.plist(5) files from the specified domain.
Depending on the current execution context, launchctl will look
in a LaunchDaemons or LaunchAgents directory for
launchd.plists. When running in the system's execution context
(i.e. when run as root via a root shell or with sudo), the
LaunchDaemons directory is searched. When running in a user's
context (i.e. run normally from a shell), the LaunchAgents
directory is searched. Valid domains are:
system
Searches /System/Library for either daemons or agents.
local
Searches /Library for either daemons or agents.
network
Searches /Network. This session type is no longer valid.
user
Searches the home directory of the calling user for agents
only. Daemons may not be loaded from this
domain.