freebsd stable - Aug 2017 - pkg issue after FreeBSD 11 upgrade

On Wed, Aug 30, 2017 at 09:00:55AM -0300, Cassiano Peixoto
wrote:
> Hi Matthew,
> 
> Sorry back to this subject. But I really need to restart services with a
> port. I'm quite sure there is a bug with pkg and FreeBSD 11.
> 
> I made a simple port to restart cron service:
It is not a bug, it is by design, pkg becomes the reaper of the scripts it runs
and kills everything once the script is executed.

btw if you install crontab in cron.d you do not need to restart the service,
cron will figure out itself and reload what it needed.

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/13bdd0ba/attachment.sig>

Hi Baptiste,

Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only.

Cron is just an example, I manage more than 50 FreeBSD servers, and I've
been using ports for years to update some configs and restart the service
on all of them. Many times I need to change nginx config, ldap, etc. I just
need to restart the service.

Is there some flag to disable it? Or some hack that I could do?

Thanks.



On Wed, Aug 30, 2017 at 9:48 AM, Baptiste Daroussin <bapt at freebsd.org>
wrote:
> On Wed, Aug 30, 2017 at 09:00:55AM -0300, Cassiano Peixoto wrote:
> > Hi Matthew,
> >
> > Sorry back to this subject. But I really need to restart services with
a
> > port. I'm quite sure there is a bug with pkg and FreeBSD 11.
> >
> > I made a simple port to restart cron service:
>
> It is not a bug, it is by design, pkg becomes the reaper of the scripts it
> runs
> and kills everything once the script is executed.
>
> btw if you install crontab in cron.d you do not need to restart the
> service,
> cron will figure out itself and reload what it needed.
>
> Bapt
>