Running out of clusters (due to too low kern.maxclusters) destinies you to reboot or should it self-heal? What parameters should guide one's setting of kern.maxclusters?
Dear list, Karlis and I experienced the "hangup" problem and discussed it last month on the bugs ML ( all the thread at http://marc.info/?l=openbsd-bugs&m=137321082217664&w=2 ). Claudio had the kindness to point out that having no available clusters (i.e. a kern.maxclusters setting set too low for the machine's network load in a given moment) would bring a state matching our description of the "hangup" problem. Though, it would make sense that the problem (= TCP stack not accepting new incoming connections, and some more) would *self heal* as soon as clusters/mbufs had been freed up, and this was not Karlis' and my experience. So to bring order to this reasoning, I wish to pose the question: Is the TCP stack implemented in such a way that clusters running out [because of a too low kern.maxclusters setting for a particlar network load] may lead to permanent breakdown of its state and thus may require reboot, or should it always self-heal? And then: Now that we see that a too low kern.maxclusters setting for a particular server load may make the TCP stack fail temporarily - or permanently? - , we get to the question: What are the guidelines for choosing kern.maxclusters setting - how should number of incoming TCP connections per second, number of concurrent TCP connections, their throughput, and any other relevant parameters, impact the choice of kern.maxclusters ? Thanks and best regards, Mikael
EuroBSDCon 2013
I would be great if someone could record the OpenBSD videos for EuroBSDCon 2013 and post them on youtube. I'm particularly interested in the Y2038: Going long long on time_t to cope with 2,147,483,647+1 talk. No offence meant to the VM/VFS hackers out there :-) -- This message is strictly personal and the opinions expressed do not represent those of my employers, either past or present.
Re: 10G NIC recommendation
sounds like I already have the cards I need in myx(4). I'm currently using them for 10g packet capture systems under a Linux install using their proprietary snf driver. Slick driver, but it is proprietary, Myri only supports Linux/FreeBSD and Winders with it. Will be interesting to see how well pflog can keep up with 5G full duplex stream. thanks for the feedback diana Past hissy-fits are not a predictor of future hissy-fits. Nick Holland(06 Dec 2005)
Re: Other mailers failing on spamd's 451?
On 2013-08-14 13:43, Nick Holland wrote: > Anyone else having a problem with their spamd-protected mail servers > being unable to receive mail from a number of mail services due to them > immediately giving up on a 451 error? > ... > > Anyone else experiencing this? Yes, unfortunately. I can't recall any particular culprits off the top of my head, but it happens from time to time. Very annoying, it's hard to explain to my customers that although "it works when they mail me at home" the problem actually isn't at our end but with the sender not respecting the protocol specification. I hate to have to whitelist entire mail providers just because of this issue, but I haven't figured out anything better to do. I guess the problem is that RFC 821/2821/5321 specifiecs the retry action on a 451 as a "SHOULD" and not a "MUST" requirement, and that hint obviously isn't strong enough for some... Regards, /Benny -- internetlabbet.se / work: +46 8 551 124 80 / "Words must Benny Lofgren/ mobile: +46 70 718 11 90 / be weighed, / fax:+46 8 551 124 89/not counted." /email: benny -at- internetlabbet.se
Re: yacc(1) LALR reference
On Aug 12 07:12:17, j...@kerhand.co.uk wrote: > On Sun, Aug 11, 2013 at 11:01:44PM +0200, Jan Stary wrote: > > This diff to yacc(1) adds a reference to the original LALR(1) paper. > > I am not sure about the markup, as mandoc render it as > > > > F. DeRemer and T. J. Pennello, "Efficient Computation of LALR(1) > > Look-Ahead Sets", 4, TOPLAS, 4, 615-649, 1982. > > > > Note the order: issue number, journal name, volume number. > > Is that expected? Should I just make it "issue 4:4"? > > > > i would just use %A, %D, %T, and %J myself. The original diff is not even correct (%I is not the issue number, %N is). I am using the n-dash for the page range, because that's what I have seen in other .Rs blocks. Is that preffered, or should that be simply 123-456? Jan Index: usr.bin/yacc/yacc.1 === RCS file: /cvs/src/usr.bin/yacc/yacc.1,v retrieving revision 1.26 diff -u -p -r1.26 yacc.1 --- usr.bin/yacc/yacc.1 18 Oct 2010 14:42:16 - 1.26 +++ usr.bin/yacc/yacc.1 15 Aug 2013 10:49:38 - @@ -182,6 +182,16 @@ conflicts, the number of conflicts is al to the standard error. .Sh SEE ALSO .Xr yyfix 1 +.Rs +.%A F. DeRemer +.%A T. J. Pennello +.%T Efficient Computation of LALR(1) Look-Ahead Sets +.%J TOPLAS +.%V 4 +.%N 4 +.%D 1982 +.%P 615\(en649 +.Re .Sh STANDARDS The .Nm
Re: VirtualBox+chive+mysql
On Wed, Aug 14, 2013 at 4:48 PM, Bruno Flueckiger wrote: > On 14.08.2013 14:21, Tony Berth wrote: > >> Dear group, >> >> I have following configuration: >> >> - latest Ubuntu amd64 server >> - VirtualBox running on the above Ubuntu server >> - openbsd 5.3 (amd64) with mysql and chive installed and running inside >> VirtualBox >> >> when I try to connect to the openbsd mysql server from mysql workbench >> installed in Ubuntu, everything works fine. >> When I try the same but calling chive from the openbsd installation, I get >> 'CDbConnection failed to open the DB connection'. What is the difference? >> >> Thanks >> > > > Hi, > > I don't have any knowledge about mysql workbench or chive. The usual > suspects > would be: > > - Wrong hostname > - Missing DNS entry for hostname > - Wrong DNS config on the OpenBSD VM > - Wrong username > - Wrong password > > It's hard to tell where the problem if you don't provide us with more > details. > > Regards, > Bruno > > I provide exact the same credentials regardless if I connect from mysql workbench or the browser by calling chive. I tried the dynamic IP provided by VirtualBox , the domain (as listed in /etc/hosts), localhost or 127.0.0.1 and all of them failed. Using mysql workbench, was able to connect via the dynamic IP. What do you mean by 'Wrong DNS config on the OpenBSD VM'? In VirtualBox I have a 'Bridged Adapter' network setting and I'm able to access the web server from the Ubuntu box by calling the assigned dynamic IP. Thanks
Re: 10G NIC recommendation
On Thu, Aug 15, 2013 at 03:56:14PM +1000, David Gwynne wrote: > im using myx(4). im biased though. Only ix(4), myx(4) and maybe oce(4) are viable options. ixgb(4) is pci-x only and slow. tht(4) has its own sets of issues and is not really available on the market anymore. xge(4) may work but is not popular and che(4) is not working at all. -- :wq Claudio > On 15/08/2013, at 9:09 AM, Diana Eichert wrote: > > > What I want to do. > > > > create a netflow collector using OpenBSD by looking at > > data fed from a tap > > > > I know which 10G NICs are supported by OpenBSD, what I'd > > like to hear is a recommendation on which one of the > > following to use. > > > > $ apropos 10G > > che, cheg (4) - Chelsio Communications 10Gb Ethernet device > > ix (4) - Intel 82598/82599/X540 PCI Express 10Gb Ethernet device > > ixgb (4) - Intel PRO/10GbE 10Gb Ethernet device > > myx (4) - Myricom Myri-10G PCI Express 10Gb Ethernet device > > oce (4) - Emulex OneConnect 10Gb Ethernet device > > tht, thtc (4) - Tehuti Networks 10Gb Ethernet device > > xge (4) - Neterion Xframe/Xframe II 10Gb Ethernet device > > > > I do have a few Myricom 10G-PCIE2-8B2-2S available already. > > However I have funds available to get something else if one > > of the other cards performs better. > > > > thanks > > > > diana > > > > > > Past hissy-fits are not a predictor of future hissy-fits. > > Nick Holland(06 Dec 2005)
