cudadog / coreemu

Automatically exported from code.google.com/p/coreemu
BSD 2-Clause "Simplified" License
0 stars 0 forks source link

EMANE unable to use realtime mode when started from init script on Fedora 15 #102

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
When cored.py is started from the /etc/init.d/core script with an EMANE 
scenario, EMANE fails with:
  "ABORT could not set sceduler <sic> to realtime"

http://pf.itd.nrl.navy.mil/pipermail/core-users/2012-January/000763.html

This occurs with CORE 4.2 or svn and EMANE 0.7.2 on Fedora 15 i686/x86_64.

The workaround is to start cored.py manually from a root terminal.

Original issue reported on code.google.com by ahrenh...@gmail.com on 11 Jan 2012 at 6:50

GoogleCodeExporter commented 9 years ago
also seems to affect Fedora 16 with EMANE 0.7.4

CORE + EMANE works when manually starting cored.py as root.

init script should be turned into a systemd profile

another related issue is when you try 'service core start', then 'service core 
stop', then 'service core start' again, the coredpy.log reports "terminated by 
signal: 15"

Original comment by ahrenh...@gmail.com on 5 Sep 2012 at 4:34

GoogleCodeExporter commented 9 years ago
systemd launches processes in their own cgroup; probably need to configure the 
cgroup with cored.py to allow real-time scheduling

another workaround is setting "emane_realtime = False" in core.conf

wrote a systemd service file, but the EMANE problem remains

Original comment by ahrenh...@gmail.com on 5 Sep 2012 at 7:45

GoogleCodeExporter commented 9 years ago
RPM has been updated to turn off emane_realtime in core.conf file, and to 
include a systemd startup script.

The original issue still remains, but now the default installed behavior won't 
be so broken.

Original comment by ahrenh...@gmail.com on 6 Sep 2012 at 2:09