The siproxd.conf.example bundled with siproxd contains references to the dirs /usr/lib/siproxd and /var/run/siproxd, neither of which are created by the current 0.5.11 ebuild. /var/lib/siproxd is used for a persistant state file which keeps track of SIP registrations (apparently), and is an optional dir for siproxd to chroot to. /var/run/siproxd is the default directory to store the PIDfile in. siproxd doesn't work properly without changing the default config file unless these directories are present. Because I was adding these dirs, I figured that it wouldn't hurt to have an actual "siproxd" user for the daemon to run as, instead of just "nobody," so I've added that into the ebuild as well, and made sure that the two new dirs were owned by that user. Additionally, the default conf file specifies /var/run/siproxd as the directory to store the PID file, but the included init script had just been using /var/run. I've fixed that as well. I'll attach patches momentarily. Reproducible: Always Steps to Reproduce:
Created attachment 62162 [details, diff] siproxd-0.5.11-r1.patch Here's the patch to the ebuild itself
Created attachment 62164 [details, diff] siproxd.rc6.patch ... and here's a patch for the init script
*** Bug 97473 has been marked as a duplicate of this bug. ***
changes have been added to the ebuild, thanks a lot
