[MacPorts] #67955: startupitem: enhancement: logfile should also log to stderr (was: startupitem: enhancements: logfile should also log to stderr; add user/group capabilities)

MacPorts noreply at macports.org
Wed Aug 16 23:12:17 UTC 2023


#67955: startupitem: enhancement: logfile should also log to stderr
--------------------------+-------------------------
  Reporter:  mascguy      |      Owner:  (none)
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  base         |    Version:  2.8.1
Resolution:               |   Keywords:  startupitem
      Port:               |
--------------------------+-------------------------
Description changed by mascguy:

Old description:

> A few suggested enhancements, which would further improve `startupitem`
> functionality:
>
> * `startupitem.logfile`: This option only enables stdout logging, via
> `StandardOutPath`. It should also log stderr, via `StandardErrorPath`.
> * Presently, there is no built-in capability to support a custom user
> and/or group, requiring each port to implement this via various means.
> (Generally either via `su`, or a custom plist file.) But ideally, a port
> should be able to enable such functionality via optional properties.
> (Say, `startupitem.run_user` and `startupitem.run_group`, or something
> similar.)
>
> Some ideas/assumptions about the latter:
> * Specifying a custom user and/or group, would not be supported with a
> custom plist file.
> * Depending on macOS version support, this could potentially be
> accomplished at the `launchd` level, via properties `GroupName` and
> `UserName`. Alternatively, it could be done by wrapping commands via
> `su`. (Or whichever method is most appropriate, to support the full swath
> of macOS releases.)

New description:

 `startupitem.logfile`: This option only enables stdout logging, via
 `StandardOutPath`. It should also log to stderr, via `StandardErrorPath`.

 AFAIK (?) - and based on local testing - it appears that it's OK to log
 both to the same file. But if anyone's aware of any cases where that can
 be problematic, please don't hesitate to speak up.

--

-- 
Ticket URL: <https://trac.macports.org/ticket/67955#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list