On 02/28/2011 01:55 AM, Trent W. Buck wrote: > Daniel Lezcano<daniel.lezc...@free.fr> writes: > >> I was using dnsmasq as a dns and a dhcp server and sending the >> hostname as an identifier for the dhcp protocol, so I was able to >> reach the container without taking care of the ip address / mac >> address. But I noticed dnsmasq was collapsing and taking a very long >> time before sending an ip address after ~ 600 containers. > This interests me: do you attribute it to scalability issues in dnsmasq? > I use it heavily in /24 networks (i.e.<254 hosts), and it'd be good to > know in advance if it won't handle a /16 network.
It handles this number of containers but when the number reach ~600 containers it seems to collapse. I didn't investigate more, maybe the problem is not coming from dnsmasq but from the routing cache table overflow. I am waiting some feedbacks from Andre with the kernel boot option. So he should say if he is facing the same problem with dnsmasq or not. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
