Hello, I have an update. I have talked to the head developer of
InspIRCd, Sadie and figured out a few things.
Firstly, the PID is not required for the sslrehashsignal module as you
can send the required signal using systemd, systemctl kill
--signal=SIGUSR1 inspircd.service. So you can keep the --nopid flag in
the systemd service, that is not an issue.
However, the logging is broken because you do not pass --system at
configure. Instead you define directories which logdir is not accounted
for so it ends up as /usr/lib/inspircd/logs/ instead of
/var/log/inspircd/ in the AppArmor profile, as this profile is
automatically generated at compile time based on the directories that
are defined.
In ./configure do *not* pass prefix, config-dir, module-dir,
example-dir, data-dir, and binary-dir. Just pass *--system* and it will
account for these system-wide directories. Please see
https://docs.inspircd.org/packaging/ for more information on how to
package inspircd.
Also FYI, the <power> and <channels> configuration options in the
/etc/inspircd/inspircd.conf you ship are deprecated, you should probably
remove those to prevent issues in the future when InspIRCd is updated.
Thank you,
Victor Coss
On 7/12/2023 11:21 PM, Debian Bug Tracking System wrote:
Thank you for filing a new Bug report with Debian.
You can follow progress on this Bug here:
1040954:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040954.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
Filippo Giunchedi<fili...@debian.org>
If you wish to submit further information on this problem, please
send it to1040...@bugs.debian.org.
Please do not send mail toow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.
