On Monday, April 9, 2012 9:39:54 AM UTC-5, [email protected] wrote:
> On Apr 8, 8:09 pm, Adam Skutt wrote:
> > On Apr 8, 5:52 pm, [email protected] wrote:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > > On Sunday, April 8, 2012 3:55:41 PM UTC-5, Adam Skutt wrote:
> > > > On Apr 8, 2:45 pm, "superha
On Apr 8, 8:09 pm, Adam Skutt wrote:
> On Apr 8, 5:52 pm, [email protected] wrote:
>
>
>
>
>
>
>
>
>
> > On Sunday, April 8, 2012 3:55:41 PM UTC-5, Adam Skutt wrote:
> > > On Apr 8, 2:45 pm, "[email protected]"
> > > wrote:
> > > > I am using the python module nfqueue-bindings which is a
On Apr 8, 5:52 pm, [email protected] wrote:
> On Sunday, April 8, 2012 3:55:41 PM UTC-5, Adam Skutt wrote:
> > On Apr 8, 2:45 pm, "[email protected]"
> > wrote:
> > > I am using the python module nfqueue-bindings which is a nfqueue
> > > packet intercepting module. It uses the following s
On Sunday, April 8, 2012 3:55:41 PM UTC-5, Adam Skutt wrote:
> On Apr 8, 2:45 pm, "[email protected]"
> wrote:
> > I am using the python module nfqueue-bindings which is a nfqueue
> > packet intercepting module. It uses the following snippet of code to
> > start the process:
> >
> > print "tr
On Apr 8, 2:45 pm, "[email protected]"
wrote:
> I am using the python module nfqueue-bindings which is a nfqueue
> packet intercepting module. It uses the following snippet of code to
> start the process:
>
> print "trying to run"
> try:
> q.try_run()
> except KeyboardInterrupt, e:
I am using the python module nfqueue-bindings which is a nfqueue
packet intercepting module. It uses the following snippet of code to
start the process:
print "trying to run"
try:
q.try_run()
except KeyboardInterrupt, e:
print "interrupted"
The q.try_run() method blocks. I would
