chd.heemeyer.club dumped core - see /var/crash/vmcore.8
Sat Feb 4 09:01:35 MSK 2017
FreeBSD chd.heemeyer.club 12.0-CURRENT FreeBSD 12.0-CURRENT #237
r313172+c19dc6ff09(lemul): Fri Feb 3 22:38:44 MSK 2017
r...@chd.heemeyer.club:/home/rootobj/home/git/head/sys/YOY amd64
panic:
GNU gdb
Committed as r313160.
Thanks!
Pedro.
On 2/3/2017 3:24 AM, Guy Yur wrote:
Hi,
In openresolv 3.9.0, the only RESTARTCMD pattern left is @RESTARTCMD@.
The '@RESTARTCMD something@' pattern was dropped from pdns_recursor.in.
r312992 removed RESTARTCMD_WITH_ARG for @RESTARTCMD something@ but
Yes just tested this and it is how it works.
Thanks for the explanation.
Ultima
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
On Fri, Feb 03, 2017 at 10:27:48AM -0500, Ultima wrote:
> Hey Gary,
>
> You are probably right. Do you know how to "lock" this property by chance?
> I'v read this exact line several times trying to understand the exact
> meaning. The "user is allowed to change the limit" I *think* is referring
>
Hey Gary,
You are probably right. Do you know how to "lock" this property by chance?
I'v read this exact line several times trying to understand the exact
meaning. The "user is allowed to change the limit" I *think* is referring
to the zfs allow command. The problem is that I checked the dataset
On Thu, Feb 02, 2017 at 09:31:58PM -0500, Ultima wrote:
> I recently moved some data on a box with limited space. I decided I should
> limit the snapshots so that space would not become an issue. I just check
> back a week later to find out the box is hitting the borderline. Doing I
> quick check
Hi,
In openresolv 3.9.0, the only RESTARTCMD pattern left is @RESTARTCMD@.
The '@RESTARTCMD something@' pattern was dropped from pdns_recursor.in.
r312992 removed RESTARTCMD_WITH_ARG for @RESTARTCMD something@ but
reverted the sed to be '@RESTARTCMD \(.*\)@' and RESTARTCMD= to be
the value of
