> On 6 Jun 2017, at 12:51, Jonathan Gray wrote:
> While chromium, firefox, lua(sec), java, go, ftp(1), curl, wget,
> and others when acting as TLS clients all manage to get it right.
>
> Both apache 2.4.25 and nginx 1.10.2p from ports do not strictly
> enforce this on the server side but httpd(8)
> On 06 Jan 2016, at 18:49, Reyk Floeter wrote:
> - I didn't work on m4.10xlarge (see cvs:~reyk/dmesg.m4.10xlarge).
I didn’t see any mentions of it in the dmesg
https://gist.github.com/reyk/b372af303eb86bab3fee but could it be that those
machine classes (*x*large-ish) uses Intel NICs with SR-IO
>> I had a problem where npppd sometimes started with random
>> configurations, and resolved it by callocing the struct in subject.
>
> Thanks, committed.
Thank you, much appreciated!
> I don't think this causes a crash. Did it?
It most likely "exited normally" because of an "invalid" (because
Hi,
I had a problem where npppd sometimes started with random configurations, and
resolved it by callocing the struct in subject.
Cheers!
Anders
--- /usr/src/usr.sbin/npppd/npppd/parse.y.orig Wed May 7 09:25:49 2014
+++ /usr/src/usr.sbin/npppd/npppd/parse.y Wed May 7 09:26:20 2014
@@
We tried to get pflow running in a non-default rdomain, and found this to get
it going. Make sense?
--- sys/net/if_pflow.c.orig Fri Sep 13 20:58:40 2013
+++ sys/net/if_pflow.c Mon Sep 16 13:25:54 2013
@@ -1213,6 +1213,8 @@
sc->sc_if.if_opackets++;
sc->sc_if.if_obytes += m->m_
>>> The following patch clarifies that sending "r" over the FIFO doesn't
>>> produce the exact same results as SIGUSR1. Or do you prefer that we change
>>> the behaviour of the FIFO's "r" to match SIGUSR1, for example by changing
>>> ui_report() to something similar to ui_report_sa(); opening a
>>> The following patch clarifies that sending "r" over the FIFO doesn't
>>> produce the exact same results as SIGUSR1. Or do you prefer that we change
>>> the behaviour of the FIFO's "r" to match SIGUSR1, for example by changing
>>> ui_report() to something similar to ui_report_sa(); opening a
> The following patch clarifies that sending "r" over the FIFO doesn't produce
> the exact same results as SIGUSR1. Or do you prefer that we change the
> behaviour of the FIFO's "r" to match SIGUSR1, for example by changing
> ui_report() to something similar to ui_report_sa(); opening a file, an
The following patch clarifies that sending "r" over the FIFO doesn't produce
the exact same results as SIGUSR1. Or do you prefer that we change the
behaviour of the FIFO's "r" to match SIGUSR1, for example by changing
ui_report() to something similar to ui_report_sa(); opening a file, and rewrit
We experienced a "quirk" with persistence and multiple listen addresses on
redirects, such as listening to both port 21 and a passive port range for load
balancing FTP, because the session's stickiness seems to operate per-pass-rule.
One solution would be group all rules as matches under one pas
This patch adds 1GE SFP+ media support to Intel's 82599_SFP.
I wasn't able to find a 1GE SFP/SFP+ LR (single mode) optic module for 82599,
and therefore needed to bring my E10GSFPLR optics down in speed (possible in
some other operating systems).
Some notes:
* The patch is extensively tested o
> Here is a diff to support the newer Broadcom chips seen in Dell and HP
> servers. This was tested against a BCM57765, BCM5721, and BCM5720.
I've been running the code that was brought back yesterday/today on four Dell
R320s with 5720s on semi-production servers (router setup with BGP and OSPF)
>> dev_t dev = makedev(40, i); // from MAKEDEV :(
>
> 40 is incorrect. It is MD.
>
> /usr/src/etc/etc.alpha/MAKEDEV: M tun$U c 7 $U 600
> /usr/src/etc/etc.amd64/MAKEDEV: M tun$U c 40 $U 600
Thanks, guess I'd better use system("cd /dev; sh MAKEDEV tunX");
> unit = 13;
>if ((fd = open("/dev/tun0", O_RDONLY)) == -1)
>err(1, "failed to open /dev/tun0");
>if (ioctl(fd, TUNSIFUNIT, &unit) == -1)
>err(1, "ioctl failed");
I like it. I've got a few questions from npppd and openvpn users hitting the 4
t
On Sep 3, 2012, at 8:14 PM, Claudio Jeker wrote:
> I never got any negative test results back about this change. I assume
> that either nobody is interested or that it just works.
I've been using this in semi-production with announce restart yes without
issues.
15 matches
Mail list logo