search

guidotack / coreemu

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

/etc/init.d/core stop doesn't stop process #88

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. start cored using /etc/init.d/core start. 
2. run a CORE experiment
3. stop the CORE experiment
4. make a change to /etc/core/core.conf . e.g. comment out 
controlnet=172.16.0.0./24
5. stop cored using /etc/init.d/core stop

Example terminal change

duc@duc-VirtualBox:/tmp$ sudo vi /etc/core/core.conf 
duc@duc-VirtualBox:/tmp$ sudo /etc/init.d/core stop
 * Shutting down CORE services                                                     /sbin/start-stop-daemon: warning: failed to kill 28696: No such process
duc@duc-VirtualBox:/tmp$ ps -ef | grep cored
root     21109     1  0 14:25 ?        00:00:01 /usr/bin/python 
/usr/sbin/cored.py -d
duc      32190 15052  0 14:28 pts/2    00:00:00 grep --color=auto cored

What is the expected output? What do you see instead?

CORE services should shutdown properly

What version of the product are you using? On what operating system?
4.2 (20110818)

Please provide any additional information below.

This might not be the exact set of instructions.

Original issue reported on code.google.com by ducleot...@gmail.com on 31 Oct 2011 at 6:33

GoogleCodeExporter commented 9 years ago 
could not reproduce on Ubuntu 11.10 x86_64 using latest core 4.2svn5; the init 
script contains no differences since 4.2

which operating system are you using?

do you know why the value in the PID file /var/run/coredpy.pid does not match 
the pid of the running process?

Original comment by ahrenh...@gmail.com on 22 Dec 2011 at 12:25

GoogleCodeExporter commented 9 years ago 
still awaiting response to comments

will mark as invalid soon due to unreproduceability

Original comment by ahrenh...@gmail.com on 6 Jan 2012 at 7:22

GoogleCodeExporter commented 9 years ago 
Hey, sorry for the late reply. I was unable to reproduce as well It might be 
some errant thing I missed. Thanks!

Original comment by ducleot...@gmail.com on 6 Jan 2012 at 7:24

GoogleCodeExporter commented 9 years ago 
No problem. Thank you for reporting the issue!

For now I'll mark it as invalid, but at least we have a record of the issue if 
it comes up again in the future.

Original comment by ahrenh...@gmail.com on 6 Jan 2012 at 7:29