<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 9/01/2017, at 9:36 PM, Răzvan Crainea <<a href="mailto:razvan@opensips.org" class="">razvan@opensips.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hello, Nathan!<br class=""></div></div></blockquote><div><br class=""></div><div>Hi!</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">You have my answer inline.<br class=""></div></div></blockquote><div><br class=""></div><div>Likewise.</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">On 01/07/2017 11:10 AM, Nathan Ward wrote:<br class=""><blockquote type="cite" class="">Hi,<br class=""><br class="">I am running OpenSIPS 2.2.2 from RPMs from the <a href="http://opensips.org" class="">opensips.org</a> yum server.<br class=""><br class="">I am trying to find out where the SPEC files to generate the CentOS (/el7) RPMs are. I don’t seem to be able to find these in GitHub. Can someone help with this?<br class=""></blockquote>Nick (CC'ed) is maintaining the SPECS for the CentOS RPMs, but I am not sure all changes are integrated in the RPM files. But AFAIK, they are based on the public specs here:<br class=""><a href="https://github.com/OpenSIPS/opensips/blob/2.2/packaging/rpm/opensips.spec.CentOS" class=""> https://github.com/OpenSIPS/opensips/blob/2.2/packaging/rpm/opensips.spec.CentOS</a><br class=""></div></div></blockquote><div><br class=""></div><div><div class="">I don’t believe this to be the case, as the “Version:” line says 2.2.0, while the published RPMs are 2.2.2.</div></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class="">I am hoping to submit a PR to move the ‘opensips’ binary to /usr/libexec, rather than a common $PATH location. We have had a problem where this binary was mistakenly run, rather than opensipsctl. Typically, daemon binaries that do not generally get run by users should be in /usr/libexec so that they are only very intentionally executed. This should probably go in to at the very least a minor version change as it may break some people’s custom init scripts etc.<br class=""></blockquote>I am not sure I fully agree with this. /usr/libexec contain binaries that should never be run as stand-alone. But that is not OpenSIPS' case, where you can easily start it in debug mode or smth like that. For example, a similar daemon is sshd, which is located in /usr/sbin/sshd. However, internally triggered binaries, such as sftp-server are located in /usr/libexec/openssh/sftp-server. This exec should never be executed outside sshd.<br class=""></div></div></blockquote><div><br class=""></div><div>Hmmm, I’ve seen other applications ship with the daemon binary in libexec.. though I can’t recall what it was off the top of my head. It seemed a sensible thing to do. It would be unusual on a production system to run the daemon binary as a user, stashing it off to the side means it’ll only be run when very clearly intended.</div><div><br class=""></div><div>I am curious, why did “opensips monitor” allow it to run - I would have expected that to reject “monitor”.. the man page for “opensips” has nothing about accepting an argument like that. Perhaps a partial solution to this would be preventing the binary from running if there are unrecognised arguments?</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class="">On my search, I note change 9e406b2b3acfd61b39ba9679f0a599b95f56f5c2 under the 2.2.2 tag, which appears to be done with something like:<br class="">sed ’s/2.2.1/2.2.2/‘<br class=""><br class="">Note the matches where . is ‘any’ not a literal period, so there are a lot of dates that get messed up:<br class=""> -* Mon Oct 12.2.19 Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org" class="">bogdan@opensips.org</a>><br class=""> +* Mon Oct 12.2.29 Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org" class="">bogdan@opensips.org</a>><br class=""></blockquote>You are right, this is a bug in my changelog update script. I will update it now.<br class=""></div></div></blockquote><br class=""></div><div>Great :)</div><div><br class=""></div><div class=""><div class="">--</div><div class="">Nathan Ward</div></div></body></html>