+will set the sysctl(3) kern.maxfiles (SoftResourceLimits) or kern.maxfilesperproc (HardResourceLimits)
+value in addition to the setrlimit(2) values.Type: null or signed integer Default: null Declared by: launchd.agents.<name>.config.HardResourceLimits.NumberOfProcessesThe maximum number of simultaneous processes for this user id. Setting this value in a system
wide daemon will set the sysctl(3) kern.maxproc (SoftResourceLimits) or kern.maxprocperuid
@@ -1067,18 +1067,36 @@ of conditions may be specified to selectively control whether launchd keeps a jo
multiple keys are provided, launchd ORs them, thus providing maximum flexibility to the job to refine
the logic and stall if necessary. If launchd finds no reason to restart the job, it falls back on
demand based invocation. Jobs that exit quickly and frequently when configured to be kept alive will
-be throttled to conserve system resources. Type: null or boolean or (submodule) Default: null Declared by:
+be throttled to converve system resources.Type: null or boolean or (submodule) Default: null Declared by: launchd.agents.<name>.config.LabelThis required key uniquely identifies the job to launchd. Type: string Declared by: launchd.agents.<name>.config.LaunchEventsSpecifies higher-level event types to be used as launch-on-demand event
+sources. Each sub-dictionary defines events for a particular event
+subsystem, such as "com.apple.iokit.matching", which can be used to
+launch jobs based on the appearance of nodes in the IORegistry. Each
+dictionary within the sub-dictionary specifies an event descriptor that
+is specified to each event subsystem. With this key, the job promises to
+use the xpc_set_event_stream_handler(3) API to consume events. See
+xpc_events(3) for more details on event sources. Type: null or (attribute set) Default: null Example: {
+ "com.apple.iokit.matching" = {
+ "com.apple.usb.device" = {
+ IOMatchLaunchStream = true;
+ IOProviderClass = "IOUSBDevice";
+ idProduct = "*";
+ idVendor = "*";
+ };
+ };
+}Declared by: launchd.agents.<name>.config.LaunchOnlyOnceThis optional key specifies whether the job can only be run once and only once. In other words, if the
job cannot be safely respawned without a full machine reboot, then set this key to be true. Type: null or boolean Default: null Declared by: launchd.agents.<name>.config.LimitLoadFromHostsThis configuration file only applies to hosts NOT listed with this key. Note: One should set kern.host-name kern.hostname
-name in sysctl.conf(5) for this feature to work reliably. Type: null or (list of string) Default: null Declared by: launchd.agents.<name>.config.LimitLoadFromHostsThis configuration file only applies to hosts NOT listed with this key. Note: One should set kern.hostname
+in sysctl.conf(5) for this feature to work reliably. Type: null or (list of string) Default: null Declared by: launchd.agents.<name>.config.LimitLoadToHostsThis configuration file only applies to the hosts listed with this key. Note: One should set kern.host-name kern.hostname
-name in sysctl.conf(5) for this feature to work reliably. Type: null or (list of string) Default: null Declared by: launchd.agents.<name>.config.LimitLoadToHostsThis configuration file only applies to the hosts listed with this key. Note: One should set kern.hostname
+in sysctl.conf(5) for this feature to work reliably. Type: null or (list of string) Default: null Declared by: launchd.agents.<name>.config.LimitLoadToSessionTypeThis configuration file only applies to sessions of the type specified. This key is used in concert
with the -S flag to launchctl. Type: null or string Default: null Declared by: launchd.agents.<name>.config.MachServices.ResetAtCloseIf this boolean is false, the port is recycled, thus leaving clients to remain oblivious to the
demand nature of job. If the value is set to true, clients receive port death notifications when
-the job lets go of the receive right. The port will be recreated atomically with respect to boot-strap_look_up() bootstrap_look_up()
-strap_look_up() calls, so that clients can trust that after receiving a port death notification,
+the job lets go of the receive right. The port will be recreated atomically with respect to bootstrap_look_up()
+calls, so that clients can trust that after receiving a port death notification,
the new port will have already been recreated. Setting the value to true should be done with
care. Not all clients may be able to handle this behavior. The default value is false. Type: null or boolean Default: null Declared by: |
|