search

UrDHT / PyUrDHT

Python reference implementation
11 stars 3 forks source link

force-orphan #44

Closed mmcd closed 9 years ago

mmcd commented 9 years ago

Noesis:PyUrDHT michael$ python3 main.py ping trying http://45.79.205.125:8000/api/v0/peer/ping ^Cshort [] Node up and Running set() {"id":"QmU3wkypfHVtAYHrUsrkya4hPezEghj72SB3514ziqvssd", "addr":"http://131.96.253.63:8000/", "wsAddr":"ws:/131.96.253.63:8001"} started websocket proxy short [] set() short [] set() short [] set() short [] set()

mmcd commented 9 years ago

see where the control-c is there. go me! TIMING FTW!

BrendanBenshoof commented 9 years ago

I'm not sure what just happened? Did you force the ping to fail?

mmcd commented 9 years ago

yeah I think so

mmcd commented 9 years ago

I keyboard interrupted something, but it DIDNT kill the python process.

I have no idea how that happens... but it does sometimes

nwautomator commented 9 years ago

@mmcd I think you're on a Linux box, so can you run 'script mylog.log' (or whatever you want to call it) to capture your terminal output and try to recreate what you're seeing? Feel free to email to me if you like and I'll take a look.

abrosen commented 9 years ago

I'm sorry, what was the issue?

BrendanBenshoof commented 9 years ago

It looks like this is os dependent.

Threads + processes are setup as daemon processes (subordinate to the console-attached process) so the os should be taking care of killing them when the host process dies.

I think I am going to close this for now.