Hi, everyone,
one of the systems on which we run our jail based "proServer" product failed
in a very odd way for the second time with a couple of days between the two
incidents.
We run VIMAGE based jails (a lot) and bridge them with the physical interface
of the machine.
-
cloned_interfa
Hi, all,
> Am 30.08.2017 um 09:29 schrieb Patrick M. Hausen :
> one of the systems on which we run our jail based "proServer" product failed
> in a very odd way for the second time with a couple of days between the two
> incidents.
> [...]
We found this open bug:
https://bugs.freebsd.org/bugzilla
OK, guys, more replying to myswlf ;-)
> Am 30.08.2017 um 12:04 schrieb Patrick M. Hausen :
>
> Hi, all,
>
>> Am 30.08.2017 um 09:29 schrieb Patrick M. Hausen :
>> one of the systems on which we run our jail based "proServer" product failed
>> in a very odd way for the second time with a couple o
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:
# $FreeBSD$
PORTNAME= ze
PORTVERSION=1.0
CATEGORIES= custom
MASTER_SITES= #
DISTFILES=
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
Hi,
I have an iSCSI production system that exports a large number of zvols
as the iSCSI targets. System is running FreeBSD 11.0-RELEASE-p7 and
initially all of the zvols were confugured with default volmode. I've
read that it's recommended to use them in dev mode, so the system isn't
bothere
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,
On Wed, Aug 30, 2017 at 09:55:22AM -0300, Cassiano Peixoto wrote:
> Hi Baptiste,
>
> Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only.
It only worked on FreeBSD 10 prior to 10.2, the reaper functionnality in freebsd
kernel appeared in 10.2
>
> Cron is just an example, I ma
Hi Cassiano,
> On 30. Aug 2017, at 2:55 PM, Cassiano Peixoto
> 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
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
> > 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
Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal
with when I need to restart a service without upgrading? Reaper
functionnality is a trouble for many administrators who made meta ports to
manage their servers. I really think it could be a option to be
enabled/disabled. Can y
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 a
Hi Baptiste,
> On 30. Aug 2017, at 3:05 PM, Baptiste Daroussin wrote:
>
>> 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
>
> Why and what is your use case, there is a reason why this code
Cassiano Peixoto wrote:
Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal
with when I need to restart a service without upgrading? Reaper
functionnality is a trouble for many administrators who made meta ports to
manage their servers. I really think it could be a option to
On Wed, Aug 30, 2017 at 10:07:51AM -0300, Cassiano Peixoto wrote:
> Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal
> with when I need to restart a service without upgrading? Reaper
> functionnality is a trouble for many administrators who made meta ports to
> manage their
Thank you for your support Baptiste, I really appreciate that.
As same as HANDLE_RC_SCRIPTS option the new one should be handled carefully.
Please keep us posted when it's ready.
On Wednesday, August 30, 2017, Baptiste Daroussin wrote:
> On Wed, Aug 30, 2017 at 10:07:51AM -0300, Cassiano Peixo
On 30 August 2017 at 20:49, Patrick M. Hausen wrote:
>
> The only real change relates to IF teardown and we did not change anything
> (stop/restart jails) when the outages occured.
>
> So ... the network interface driver? Probably?
>
>
>
We are using igb(4) with vlan(4), tap(4) bundled into bridg
On 30 August 2017 at 01:12, Xin LI wrote:
> I think emaste@ have fixed it in r321293. MFC?
Thanks for the note, now merged in r323044.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe,
18 matches
Mail list logo
