On Fri, 12 Oct 2018 11:56:28 +0200
Marko Cupać wrote:
> After introducing carppeer option I see incoming traffic on physical
> interfaces of both MASTER and BACKUP firewalls, as opposed to the
> situation without carppeer option, where I see incoming traffic on
> physical interface of MASTER
I can't see any recent source code changes about hyperthreading, and
presume it's still supposed to be disabled by default?
It is not disabled on an EP2C602 with two E5-2690 CPUs (Sandy Bridge
EP), I can see 32 'CPUs' in both top and systat.
Bug I presume..? Can provide dmesg, debugging info,
On 2018-10-12, Peter Kay wrote:
> I can't see any recent source code changes about hyperthreading, and
> presume it's still supposed to be disabled by default?
>
> It is not disabled on an EP2C602 with two E5-2690 CPUs (Sandy Bridge
> EP), I can see 32 'CPUs' in both top and systat.
>
> Bug I
On Thu Oct 11, 2018 at 10:44:41AM +0100, Peter Kay wrote:
> Just looking at writing a small enhancement to dhcpd, and starting to use
> gdb properly for the first time. OK, it is functional, but it's a bit
> awkward compared to graphical alternatives.
> What does everyone use? I can see ddd and
Yep, I looked at the Top source after that and saw that the inactive
CPU hiding code was backed out seven days ago.
Running a make -j32 on a port shows that only CPUs 0-15 are active. Cheers!
PK
On Fri, 12 Oct 2018 at 21:41, Stuart Henderson wrote:
>
> On 2018-10-12, Peter Kay wrote:
> > I
> It is preferable to just include the whole dmesg directly in the mail
> Better still, when it's a "sometimes works" problem, include a "diff -u"
> between the two (the context to show where the lines are added/removed).
I have pasted a "diff -u" on https://paste.debian.net/1047098/
> Very
Hello,
Not sure if this is a bug or not, so I thought I would ask misc@ first.
I was writing a script in my vmm guest that involved killing and
restarting a long running process every hour using sleep "3600", and I
noticed it ended up sleeping for 2 hours and 56 minutes, rather than an
hour.
Hi,
I have changed my CARP failover setup from default multicast to unicast
by introducing carppeer config option. Physical interfaces share /29
subnet with upstream ISP, and IP addressing is as follows:
ISP: XX.XXX.XXX.121/29
FW1: XX.XXX.XXX.122/29
FW2: XX.XXX.XXX.123/29
FW_CARP:
On 2018-10-12, Aaron Mason wrote:
> Wow, never seen a multi-port Realtek NIC before.
I have but they're usually single NIC plus switch chip, looks like this
is the real thing.
> Maybe try the card on another motherboard and see if you get the same
> symptoms.
agreed if possible.
> In any
9 matches
Mail list logo