Changes between Initial Version and Version 3 of Ticket #67955


Ignore:
Timestamp:
Aug 16, 2023, 11:12:17 PM (13 months ago)
Author:
mascguy (Christopher Nielsen)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #67955

    • Property Cc herbygillot added
    • Property Component changed from ports to base
    • Property Summary changed from startupitem: enhancements: logfile should also log to stderr; add user/group capabilities to startupitem: enhancement: logfile should also log to stderr

  • Ticket #67955 – Description

    initial v3  
    1 A few suggested enhancements, which would further improve `startupitem` functionality:
     1`startupitem.logfile`: This option only enables stdout logging, via `StandardOutPath`. It should also log to stderr, via `StandardErrorPath`.
    22
    3 * `startupitem.logfile`: This option only enables stdout logging, via `StandardOutPath`. It should also log stderr, via `StandardErrorPath`.
    4 * 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.)
    5 
    6 Some ideas/assumptions about the latter:
    7 * Specifying a custom user and/or group, would not be supported with a custom plist file.
    8 * 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.)
     3AFAIK (?) - 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.