Displaying 7 results from an estimated 7 matches for "lblcr".
2011 Jan 27
1
Best way to calculate concurrent users?
...connect with clients.
O use ipvs to balance betwaeen 2 servers does anyone have an ideia ?
With ipvs i get this results:
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP XXX.XX.X.XX:143 lblcr
-> 10.0.2.10:143 Masq 1 16 228
-> 10.0.2.11:143 Masq 1 16 184
There is others ports and stuff.
Does any one have an ideia how to get this number ?
[]'sf.rique
2014 Jun 11
2
Re: libguestfs supermin error
...ed.
> [ 1.071183] IPVS: [rr] scheduler registered.
> [ 1.072265] IPVS: [wrr] scheduler registered.
> [ 1.073429] IPVS: [lc] scheduler registered.
> [ 1.074528] IPVS: [wlc] scheduler registered.
> [ 1.075638] IPVS: [lblc] scheduler registered.
> [ 1.076826] IPVS: [lblcr] scheduler registered.
> [ 1.077994] IPVS: [dh] scheduler registered.
> [ 1.079107] IPVS: [sh] scheduler registered.
> [ 1.080190] IPVS: [sed] scheduler registered.
> [ 1.081355] IPVS: [nq] scheduler registered.
> [ 1.082520] IPv4 over IPv4 tunneling driver
> [ 1...
2014 Jun 10
2
Re: libguestfs supermin error
Hi Rich
I'm able to solve the problem regarding PAPR in libguestfs on my powerpc
ubuntu.By default the libguestfs was configuring pseries machine and
afterwards I changed it to my original machine i.e ppce500 .The changes are
performed in ./src/guestfs-internal.h file.
Thanks
On Tue, Jun 10, 2014 at 7:58 PM, Richard W.M. Jones <rjones@redhat.com>
wrote:
> On Wed, Jun 04, 2014 at
2018 Jul 26
2
net-next boot error
...VS: ipvs loaded.
> IPVS: [rr] scheduler registered.
> IPVS: [wrr] scheduler registered.
> IPVS: [lc] scheduler registered.
> IPVS: [wlc] scheduler registered.
> IPVS: [fo] scheduler registered.
> IPVS: [ovf] scheduler registered.
> IPVS: [lblc] scheduler registered.
> IPVS: [lblcr] scheduler registered.
> IPVS: [dh] scheduler registered.
> IPVS: [sh] scheduler registered.
> IPVS: [mh] scheduler registered.
> IPVS: [sed] scheduler registered.
> IPVS: [nq] scheduler registered.
> IPVS: ftp: loaded support on port[0] = 21
> IPVS: [sip] pe registered.
> i...
2018 Jul 26
2
net-next boot error
...VS: ipvs loaded.
> IPVS: [rr] scheduler registered.
> IPVS: [wrr] scheduler registered.
> IPVS: [lc] scheduler registered.
> IPVS: [wlc] scheduler registered.
> IPVS: [fo] scheduler registered.
> IPVS: [ovf] scheduler registered.
> IPVS: [lblc] scheduler registered.
> IPVS: [lblcr] scheduler registered.
> IPVS: [dh] scheduler registered.
> IPVS: [sh] scheduler registered.
> IPVS: [mh] scheduler registered.
> IPVS: [sed] scheduler registered.
> IPVS: [nq] scheduler registered.
> IPVS: ftp: loaded support on port[0] = 21
> IPVS: [sip] pe registered.
> i...
2007 Jul 13
12
XEN 3.1: critical bug: vif init failure after creating 15-17 VMs (XENBUS: Timeout connecting to device: device/vif)
We have found a critical problem with the XEN 3.1 release (for those who are running 15-20 VMs on a single server). We are using the official XEN 3.1 release on a rackable server (Dual-Core AMD Opteron, 8GB RAM).
The problem we are seeing is that intermittently vifs fail to work properly in VMs after we create around 15-17 VMs on our server (all running at the same time, created one by
2018 Jul 26
0
net-next boot error
...heduler registered.
> > IPVS: [wrr] scheduler registered.
> > IPVS: [lc] scheduler registered.
> > IPVS: [wlc] scheduler registered.
> > IPVS: [fo] scheduler registered.
> > IPVS: [ovf] scheduler registered.
> > IPVS: [lblc] scheduler registered.
> > IPVS: [lblcr] scheduler registered.
> > IPVS: [dh] scheduler registered.
> > IPVS: [sh] scheduler registered.
> > IPVS: [mh] scheduler registered.
> > IPVS: [sed] scheduler registered.
> > IPVS: [nq] scheduler registered.
> > IPVS: ftp: loaded support on port[0] = 21
> >...