anchor.diff:        description = ''
           Specifies 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.match-ing", which can be used to
  +        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
  
positive.code:       default = null;
        description = ''
          This optional key is used as a hint to <literal>launchctl(1)</literal> that it should not submit this job to launchd when
          loading a job or jobs. The value of this key does NOT reflect the current state of the job on the run-ning running
          ning system. If you wish to know whether a job is loaded in launchd, reading this key from a configura-tion configuration
          tion file yourself is not a sufficient test. You should query launchd for the presence of the job using
          the <literal>launchctl(1)</literal> list subcommand or use the ServiceManagement framework's
          <literal>SMJobCopyDictionary()</literal> method.
  
          Note that as of Mac OS X v10.6, this key's value in a configuration file conveys a default value, which
          is changed with the [-w] option of the <literal>launchctl(1)</literal> load and unload subcommands. These subcommands no
          longer modify the configuration file, so the value displayed in the configuration file is not necessar-ily necessarily
          ily the value that <literal>launchctl(1)</literal> will apply. See <literal>launchctl(1)</literal> for more information.
  
          Please also be mindful that you should only use this key if the provided on-demand and KeepAlive crite-ria criteria
          ria are insufficient to describe the conditions under which your job needs to run. The cost to have a
          job loaded in launchd is negligible, so there is no harm in loading a job which only runs once or very
          rarely.
        '';
  
negative.code:             default = null;
              description = ''
                The maximum number of open files for this process.  Setting this value in a system wide daemon
                will set the <literal>sysctl(3)</literal> kern.maxfiles (SoftResourceLimits) or kern.maxfilesperproc (HardResourceLimits)
                value in addition to the <literal>setrlimit(2)</literal> values.
              '';
            };
  
  