OK I ran your request and it looks like what I had suspected... LOTS of
socket connects being made but none of them are closing. I think it's
because I connected to the machine_server.py program I had made with
twisted and the twisted instance it's closing. What are my solutions?
I think the idea situation would be to use the amp protocal builder
directly to create the communication, but I don't know how to do that.
this is why I start up twisted to send the message. :( Really need
some help here as it is WAY beyond my knowledge.
Best regards,
Jason
On 10/07/2010 10:17 AM, ron_m wrote:
Do you run on Linux? If so it is very easy to see which files are open
to a process. If you start web2py with python web2py.py and use the
built in Rocket web server you should be able to find the pid of the
python process with
$ ps -ef | grep python
Once you have the pid you can cd /proc/pid and do an ls -l fd which
will show you a list of fd number symlinks pointing to the real files
that are open for each fd (file descriptor from C open). You could
also try lsof -p pid but it will show memory mapping for shared
libraries. The ls -l fd under /proc shows 10 files on my idle
development server and lsof -l pid shows 90 files, mostly libraries
and fonts.
Ron
On Oct 6, 9:54 pm, Jason Brower<[email protected]> wrote:
Yes, this still happens over time. I thought it had to do with my code,
but perhaps it was something else?
Best Regards,
Jason Brower
On 10/07/2010 02:23 AM, ron_m wrote:
