It was favourable to have lease information visible without any
additional commands right after new lease has been obtained...
On 4/26/2018 11:21 PM, Daniel Melameth wrote:
> On Thu, Apr 26, 2018 at 2:11 PM, Denis wrote:
>> After upgrading 6.2amd64 -> 6.3amd64 there is no lease time info present
On Thu, Apr 26, 2018 at 11:21:57PM +0200, Infoomatic wrote:
> Hi Stuart,
> thanks for your input! Actually, I was never really satisfied with
> the stability of ntopng, so this problem of the memory leak does not
> really surprise me. However, when killing the process, which also
> means freeing
Hello Giannis and Claudio,
thank you both for dmesg and confirmation what works. The test system is
on its way, I'll report back with dmesg when it's here.
Have a nice day,
Jan
On 27/04/18 07:21, Infoomatic wrote:
> I think it is not an expected behaviour that the system does not handle any
> tcp/ip or icmp connections any more until the swap space is fully freed
> (which, in my case when ntopng used 3 out of 4GB swap, lastet for nearly 20
> minutes). IMHO, unswapping
On Thu, Apr 26, 2018 at 11:21 PM, Infoomatic wrote:
>
> thanks for your input! Actually, I was never really satisfied with the
> stability of ntopng, so this problem of the memory leak does not really
> surprise me. However, when killing the process, which also means freeing
> swap space, I think
Just a quick clarification, lo(4) says that the loopback interface
should be configured last, and /etc/netstart seems to support this
but netstart(8) says that the loopback interface is configured `before`
physical interfaces:
from netstart(8):
> netstart performs the following operations, in
A read of the script itself shows loopback initialized prior to
hardware interfaces, at least in 6.2 (haven't upgraded yet).
On Fri, 27 Apr 2018 08:21:54 -0400, Gabriel Guzman wrote:
> Just a quick clarification, lo(4) says that the loopback interface
> should be configured last, and /etc/netstar
Hello everyone,
I am sending this mail because I currently have a problem with
OpenBSD 6.2 running on a VM on an OVH server
(OpenBSD ovhvps.openstacklocal 6.2 GENERIC#132 amd64).
I followed this tutorial for the installation, since it is not
natively supported by OVH [0].
Now my problem is that
Hello.
I am not OVH expert, but from dmesg
I can't see second drive.
I see only sd0 (20480MB) connected to your VirtIO.
Dobule check that both drives are connected.
> why is it mentioning GUID and not disk path ?
It can work with drive names also, i.e:
"/dev/sd0a /"
but name may be changed when
Hi All,
Figured I'd see what happens when I load openBSD on a laptop that I
haven't used very much.
dmesg shows several 'not configured' devices, including the Atheros
AR9485 wifi card.
Looks like in March 2014 Stefan said the wifi wasn't ready yet. Given
that four years have passed, I'll proba
Greetings,
I was wondering if anybody is using the current stock qemu user-mode code
to run OpenBSD code. The code looks woefully incomplete to my eye, so
incomplete I can't see how it would work for anything useful. I'm not even
sure it would work for anything trivial.
My searching has lead me t
Hello folks,
I just tried a combination of OpenBSD, Vagrant and Virtualbox that's been
working since OpenBSD version 6.0 and the provisioning fails quite soon after I
hit "vagrant up".
Initially I thought was something regarding my own scripts, but after some
testing, I realized that anything
Based on the:
http://www.vegardno.net/2017/03/fuzzing-openssh-daemon-using-afl.html
I tried to search for these code pieces (I know he was using openbsd-compat and
not the original OpenSSH code) but didn't found it, didn't even find similar
for disabling message CRCs:
in the ( https://github.
who is "jmc" in the header? can someone cc him? or the people who are doing the
doc? :)
Many thanks.
> Sent: Friday, April 27, 2018 at 3:28 PM
> From: "Amelia A Lewis"
> To: misc@openbsd.org
> Subject: Re: /etc/netstart - order of operations (lo vs physical interfaces)
>
> A read of the script
Thanks for the reply, I have rebuilt a softraid mirror before, I was
just hoping for some clarification as the faq wording is a little
ambiguous as to whether drives can be rebuilt in multi user mode or not.
I was also curious how the system handles write operations to the array
while it is reb
Quoting Warner Losh :
Greetings,
I was wondering if anybody is using the current stock qemu user-mode code
to run OpenBSD code. The code looks woefully incomplete to my eye, so
incomplete I can't see how it would work for anything useful. I'm not even
sure it would work for anything trivial.
16 matches
Mail list logo
