Having inconsistent results, now. I went back and looked at fedora 18, remounting "/" as you directed, and the demo initially ran, provided I manually created br0 for it. The demo doesn't create/remove br0 itself as it does on the demo VM.
Now, however, the containers start, but within a few seconds, I get four lines of "not found", and running the stop script states "emane: no process found" According to the log, lxc_conf fails to attach 'veth1.0' to 'br0'…"No such device." At the end of the log, also, is an error from lxc_cgroup; no such file/directory, failed to remove cgroup '/sys/fs/cgroup/systemd/node-1, if that's relevant. ___________________________________________ James B. Morris Dept. of Electrical, Computer, and Systems Engineering [email protected] JEC 6212 Rensselaer Polytechnic Institute 110 8th St. Troy, NY 12180-3590 On Jun 25, 2013, at 11:31 AM, Steven Galgano <[email protected]> wrote: > James, > > Nothing really. Those limits are in place to keep runaway RT processes > from hogging 100% of your CPU(s). On our internal emane testbeds we > disable the limitation - understanding the consequences and placing full > faith in emane. > > -- > Steven Galgano > Adjacent Link LLC > www.adjacentlink.com > > > On 06/25/2013 11:24 AM, J. Morris wrote: >> Mounting the pseudo tty was what kept failing in Fedora. The system is >> pretty much dedicated to EMANE use; in terms of "what else" may be running >> on the system, what kinds of things may be affected by disabling those >> limits? >> >> ~James >
_______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
