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 <fra...@lastsummer.de> wrote: > Hi Cassiano, > > > On 30. Aug 2017, at 2:55 PM, Cassiano Peixoto <peixotocassi...@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 _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
