[Bug 293251] www/redmine60 use -T redmine for daemon logging in syslog

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293251

            Bug ID: 293251
           Summary: www/redmine60 use -T redmine for daemon logging in
                    syslog
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: delphij@FreeBSD.org
          Reporter: 000.fbsd@quip.cz
             Flags: maintainer-feedback?(delphij@FreeBSD.org)
          Assignee: delphij@FreeBSD.org

Created attachment 268149
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=268149&action=edit
rc.d/redmine with hardcoded -T redmine

It's more of a feature request.
I upgraded my old redmine51 installation to redmine60. As redmine60 uses Puma
instead of Thin, the logging of startup messages changed too. In the old
redmine51 I used: -l /usr/local/www/redmine/log/thin.log to have start up
logged in to file.

This was in rc.conf
redmine_flags="-l /usr/local/www/redmine/log/thin.log -a 0.0.0.0 -p 8080 -e
production"

But with redmine60, there is redmine_args instead and the start of the Puma is
made by "daemon". All messages go to syslog under "daemon" facility with tag
"daemon", so they are written in /var/log/message and /var/log/daemon.log (if
enabled):

Feb 17 23:58:01 alpha daemon[56818]: Puma starting in single mode...
Feb 17 23:58:01 alpha daemon[56818]: * Puma version: 7.1.0 ("Neon Witch")
Feb 17 23:58:01 alpha daemon[56818]: * Ruby version: ruby 3.3.10 (2025-10-23
revision 343ea05002) [amd64-freebsd14]
Feb 17 23:58:01 alpha daemon[56818]: *  Min threads: 0
Feb 17 23:58:01 alpha daemon[56818]: *  Max threads: 5
Feb 17 23:58:01 alpha daemon[56818]: *  Environment: production
Feb 17 23:58:01 alpha daemon[56818]: *          PID: 56819
Feb 17 23:58:02 alpha daemon[56818]: `/` is not writable.
Feb 17 23:58:02 alpha daemon[56818]: Bundler will use
`/tmp/bundler20260217-56819-7sqqbr56819' as your home directory temporarily.
Feb 17 23:58:05 alpha daemon[56818]: * Listening on http://10.20.30.5:8080
Feb 17 23:58:05 alpha daemon[56818]: Use Ctrl-C to stop

I would like to have them tagged "redmine" to distinguish between other generic
"daemon" messages and have them in the separate redmine.log logfile (configured
in syslog.conf)

I added -T redmine into rc.d/redmine (see attached patch) and it works good
with the following change in the syslog.conf

!-redmine
*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err  
/var/log/messages

!redmine
*.*                                             /var/log/redmine.log

Now Redmine messages are tagged "redmine" and written to redmine.log

# tail -f /var/log/redmine.log
Feb 18 00:08:02 alpha redmine[63578]: * Puma version: 7.1.0 ("Neon Witch")
Feb 18 00:08:02 alpha redmine[63578]: * Ruby version: ruby 3.3.10 (2025-10-23
revision 343ea05002) [amd64-freebsd14]
Feb 18 00:08:02 alpha redmine[63578]: *  Min threads: 0
Feb 18 00:08:02 alpha redmine[63578]: *  Max threads: 5
Feb 18 00:08:02 alpha redmine[63578]: *  Environment: production
Feb 18 00:08:02 alpha redmine[63578]: *          PID: 63579
Feb 18 00:08:02 alpha redmine[63578]: `/root` is not writable.
Feb 18 00:08:02 alpha redmine[63578]: Bundler will use
`/tmp/bundler20260218-63579-mvu3zs63579' as your home directory temporarily.
Feb 18 00:08:06 alpha redmine[63578]: * Listening on http://10.20.30.5:8080
Feb 18 00:08:06 alpha redmine[63578]: Use Ctrl-C to stop

It is hardcoded now and as it changes current default behavior it may be not
acceptable for ports commit.

So the question is, how can we do it better?

Will it be better to introduce new variable to rc.conf, for example
redmine_ident, which can be changed by user to redmine_ident="redmine" in
rc.conf, set to "daemon" by default to keep the current behavior and change
command_args in rc.d/redmine to 

command_args="-c -f -P ${pidfile} -S -T ${redmine_ident}

with : ${redmine_ident="daemon"}

Will this be acceptable solution?
Or will it be better to add more generic redmine_daemon_flags="" to allow
change more / any args of the daemon?

I can create the patch I just want to know from maintainer or other people
using the redmine60 what is the best way.

-- 
You are receiving this mail because:
You are the assignee for the bug.