General notes on startup items: - In general, it is preferable to use startupitem.executable rather than any of startupitem.init, startupitem.start, startupitem.stop, startupitem.restart. If startupitem.executable is used, a pidfile path and style should also be specified. startupitem.create Choose whether or not to generate a startup item Type: optional Values: yes no Default: no Example: startupitem.create yes startupitem.type Select the type of startupitem to generate. By default, a startupitem will be generated that is of the appropriate type for the OS. For instance, launchd is favored on system 10.4, while SystemStarter is favored on prior Mac OS X systems. A global default may be specified with the startupitem_type preference in ports.conf. Type: optional Values: SystemStarter, launchd, default, rcNG Default: default Example: startupitem.type launchd startupitem.executable The name of the daemon to be run in the background. This option may contain multiple arguments, but they must be appropriate for a call to exec; they may not contain arbitrary shell code. This option may not be used together with any of the four options startupitem.init, startupitem.start, startupitem.stop and startupitem.restart. Type: optional Values: name of executable, and any arguments Example: startupitem.executable $prefix/bin/wonka startupitem.init Shell code that will be executed prior to any of the options startupitem.init, startupitem.start, startupitem.stop and startupitem.restart. Type: optional Values: sh code Example: startupitem.init FOO=start startupitem.start Shell code that should be executed to start the daemon. Type: optional Values: sh code Example: startupitem.start $prefix/share/mysql/mysql.server start startupitem.stop Shell code that should be executed to stop the daemon. Type: optional Values: sh code Example: startupitem.start $prefix/share/mysql/mysql.server stop startupitem.restart Shell code that should be executed to restart the daemon. In the absense of this key, the daemon will be restarted by taking the stop action, followed by taking the start action. Type: optional Values: sh code Example: startupitem.start $prefix/share/mysql/mysql.server restart startupitem.pidfile Specification for pidfile handling. This is particularly useful in conjunction with the startupitem.executable key, as in this case it is important that the startupitem know how to track the executable. This specifies whether the daemon generates its own pidfile (auto), whether it generates its own but forgets to delete it, so that the startupitem should delete it (clean), or whether it never generates one, in which case the startupitem should manage the pidfile on its own (manual), or whether no pidfile should be used at all (none). Type: optional Values: none|auto|manual|clean [/path/to/pidfile] Default: pidstyle defaults to "none", pidfilepath defaults to "${prefix}/var/run/${name}.pid" Example: startupitem.pidfile auto $prefix/var/run/${name}.pidfile startupitem.logfile Path to a logfile into which to log events about the lifetime of the startupitem. Depending on the type of startupitem, and the manner in which it is started, standard output from the daemon may also be directed to the logfile. Type: optional Values: path Default: /dev/null Example: startupitem.logfile $prefix/var/log/mydaemon.log startupitem.logevents Control whether or not to log events to the log file. If logevents is set, events are logged, with their time, to the logfile. Type: optional Values: yes|no Default: no Example: startupitem.logevents yes svn.url Specify the url from which to fetch files. Type: required (if subversion is going to be used) Values: a legal subversion url Default: none Examples: svn.url http://www.domain.com/svn-repo/mydirectory svn.url svn://www.domain.com/svn-repo/mydirectory svn.tag Specify the a tag from which svn should fetch files. This corresponds to the -r option to the svn cli. Type: optional Values: a legal subversion tag Default: none Examples: svn.tag 1020 svn.tag {2005-10-05} svn.tag HEAD