Hello Victor, my apologies for the late reply and thank you for the extensive bug report and research!
On Tue, Jul 18, 2023 at 08:52:38PM -0400, Victor Coss wrote: > Hello, I have another update to provide. I was able to temporarily fix file > logging until you can fix the package. I had to create a logs folder in > /usr/lib/inspircd/ and change it's permissions accordingly and change > ownership and group to irc:irc with read and write permissions so InspIRCd > can write various log files in that directory. As stated before the correct > location should be /var/log/inspircd/ for log files instead. You may need to > have the package create this directory on install and give the proper > permissions for the irc user to read and write to it. I have uploaded 3.17.0-1 just now, and allowed apparmor access to /var/log/inspircd.log as a short term fix for this issue. I'm happy to switch to /var/log/inspircd for the default log location as a followup though. > Also as a side note so you are aware, any segfaults you see in dmesg, are > not actually segmentation faults; this is caused by InspIRCd not using > standard exit codes. This can be fixed in v3 of InspIRCd by adding > -DINSPIRCD_BINARY_EXIT to CXXFLAGS in the environment to disable the custom > exit codes that InspIRCd uses. In v4 (not released yet) this has been > resolved completely and InspIRCd will use standard exit codes. Thank you for this report too, I was not aware! best, Filippo
