Hi Cassiano,> On 30. Aug 2017, at 2:55 PM, Cassiano Peixoto <peixotocassiano at gmail.com> wrote: > > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only.It was a later 10.x change as far as I know.> Is there some flag to disable it? Or some hack that I could do?No. At OPNsense we use a patch to revert the behaviour. https://github.com/opnsense/ports/blob/master/ports-mgmt/pkg/files/patch-libpkg_scripts.c Cheers, Franco
On Wed, Aug 30, 2017 at 03:01:30PM +0200, Franco Fichtner wrote:> Hi Cassiano, > > > On 30. Aug 2017, at 2:55 PM, Cassiano Peixoto <peixotocassiano at gmail.com> wrote: > > > > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. > > It was a later 10.x change as far as I know. > > > Is there some flag to disable it? Or some hack that I could do? > > No. At OPNsense we use a patch to revert the behaviour. > > https://github.com/opnsense/ports/blob/master/ports-mgmt/pkg/files/patch-libpkg_scripts.cWhy and what is your use case, there is a reason why this code has been added, and I would like to hear more about use cases so we can try to address them. Best regards, Bapt -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20170830/052f2bd0/attachment.sig>
Hi Franco, Thank you. You know what I'm suffering. As I said in my last email I think it would be an option to enable/disable. I just upgraded my customers servers to FreeBSD 11 and I just realized it. I think when more admins who maintain this kind of port (needing to restart services), as soon as they migrate they will face the same problem. On Wed, Aug 30, 2017 at 10:01 AM, Franco Fichtner <franco at lastsummer.de> wrote:> Hi Cassiano, > > > On 30. Aug 2017, at 2:55 PM, Cassiano Peixoto <peixotocassiano at gmail.com> > wrote: > > > > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. > > It was a later 10.x change as far as I know. > > > Is there some flag to disable it? Or some hack that I could do? > > No. At OPNsense we use a patch to revert the behaviour. > > https://github.com/opnsense/ports/blob/master/ports-mgmt/ > pkg/files/patch-libpkg_scripts.c > > > Cheers, > Franco