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 2
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 Debi
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 afra
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
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
_
