On Monday 13 June 2005 13:46, Ragnar Lonn wrote: > Julian Elischer wrote: > > Ragnar Lonn wrote: > >> Hello, > >> > >> I've been using vimage on FreeBSD 4.11 along with Netgraph to setup a > >> system > >> that simulates many physical client machines for the purpose of > >> testing broadband > >> Internet access hardware. I have hundreds of vimages, each with its > >> own ngeth0 > >> network interface connected via Netgraph to a real physical > >> interface. It is working > >> very well indeed but now I'm trying to setup logging from the various > >> vimage > >> instances and have run into problems. Each vimage runs applications that > >> I want to log the output from in an orderly manner. I'd like to use > >> syslog but as > >> it turns out, the processes inside a vimage cannot communicate with > >> the syslogd > >> in the "default" vimage. I tried logging to the Unix domain socket > >> /var/run/log but > >> that didn't work from within a vimage (other than "default" of course). > > > > did you ask syslog to open sockets in all the chroots? > > I assume yes.. I hadn't realised that the vimage code separates > > unix domain sockets etc. but I guess that makes sense. > > Actually, I don't chroot the vimages as of now. They see the same > filesystem all of them but writing to the syslogd unix domain socket didn't > work anyhow. > I'm both happy and frustrated at seeing how well separated vimages are > sometimes :-) >
Are you talking about Marko Zec's network virtualisation patch? If yes, then you need one simple patch to allow AF_UNIX (named pipes) to work between images. I do not have it at hand now, but if you need it, I could search my archives... Regards, Milan _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
