Re: [nox-dev] Signals (SIGHUP) sent to applications?
On Nov 24, 2008, at 24:43 , Martin Casado wrote:
Hmm, Teemu thinks he's fixed that in our local branch which probably
doesn't do you much good atm.
You could always register a handler in C++ if you don't mind
a temporary hack you can just add it to src/nox_main.cc
.martin
On Nov 23, 2008, at 12:43 PM, Glen Gibb wrote:
I'm afraid that trying to use signal gives the following error:
ValueError: signal only works in main thread
Actually, this specific problem doesn't have a cure in our local
branch, but one can work around it using the reactor.callFromThread
call which executes a function within the reactor's thread. The
example below worked just fine on our local branch and it *should*
work with the noxrepo.org version too:
def sig_install():
def sig_handler(signal_num, handler):
lg.debug('HUP!')
import signal
signal.signal(signal.SIGHUP, sig_handler)
from twisted.internet import reactor
reactor.callFromThread(sig_install)
HTH,
Teemu
--
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] openflow switch issue regarding kernel space installation
Hi, Siraj. Did you type "--with-l26=/path/to/linux-2.6/" in directly or did you give it the correct path to your kernel headers? On Debian, you'd probably want to run it like this: ./configure --with-l26=/lib/modules/`uname -r`/build The OpenFlow wiki has full instructions for Debian: http://openflowswitch.org/wk/index.php/Debian_Install By the way, this mailing list is really focused on NOX, which is a controller for OpenFlow. There are a lot of OpenFlow developers on this mailing list, but questions specific to OpenFlow should probably go to them. It doesn't appear that there's a general mailing list at openflowswitch.org, so I'll ping them about that... Also, you'll need a newer version of OpenFlow than is available on openflowswitch.org. I'd recommend the following: http://noxrepo.org/releases/openflow-0.9.0~b1.tar.gz In the very near future, the OpenFlow consortium will be releasing v0.8.9, which will be compatible with NOX. Until then, you'll need to use the tarball shown above. Good luck. Let me know if you continue to have issues. --Justin On Nov 23, 2008, at 2:14 PM, siraj rathore wrote: Dear Sir I am PhD student at Royal Institute of technology Sweden. I am interested to learn about openflow switches and to do research in this field. I am facing problem regarding Kernel based open flow installation. i am using Debian unstable kernel 2.6.26. To build open flow switch in kernel space i executed following commands according to instructions given on the nox and open flow websites. ( i am using openflow version 0.8.2) ./configure --with-l26=/path/to/linux-2.6/ make In result following binaries are created openflow-v0.8.2/secchan/secchan openflow-v0.8.2/utilities/dpctl openflow-v0.8.2/controller/controller But openflow-v0.8.2/datapath/linux-2.6/openflow_mod.ko "openflow_mod.ko" is not present there. Therefore i could not load kernel space switch. Can you guide me to solve this issue. Regards Siraj ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] Signals (SIGHUP) sent to applications?
Hmm, Teemu thinks he's fixed that in our local branch which probably doesn't do you much good atm. You could always register a handler in C++ if you don't mind a temporary hack you can just add it to src/nox_main.cc .martin On Nov 23, 2008, at 12:43 PM, Glen Gibb wrote: I'm afraid that trying to use signal gives the following error: ValueError: signal only works in main thread Martin Casado wrote: I think import signal signal(signal.SIGHUP, foo) should work. Is there an easy way to get a Nox python application to respond to SIGHUP? Thanks, Glen ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
[nox-dev] openflow switch issue regarding kernel space installation
Dear Sir I am PhD student at Royal Institute of technology Sweden. I am interested to learn about openflow switches and to do research in this field. I am facing problem regarding Kernel based open flow installation. i am using Debian unstable kernel 2.6.26. To build open flow switch in kernel space i executed following commands according to instructions given on the nox and open flow websites. ( i am using openflow version 0.8.2) ./configure --with-l26=/path/to/linux-2.6/ make In result following binaries are created openflow-v0.8.2/secchan/secchan openflow-v0.8.2/utilities/dpctl openflow-v0.8.2/controller/controller But openflow-v0.8.2/datapath/linux-2.6/openflow_mod.ko "openflow_mod.ko" is not present there. Therefore i could not load kernel space switch. Can you guide me to solve this issue. Regards Siraj ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] Signals (SIGHUP) sent to applications?
I'm afraid that trying to use signal gives the following error: ValueError: signal only works in main thread Martin Casado wrote: I think import signal signal(signal.SIGHUP, foo) should work. Is there an easy way to get a Nox python application to respond to SIGHUP? Thanks, Glen ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
