Hi Jirka, Thank you for your quickly reply.
> this is technically impossible, two programs cannot listen on the > same TCP port (on one interface). It's very likely that it was Django > webserver listening there. You are right, sorry for that stupid question, and I check it again, I find the Xvnc process used the 8000 port and killed the Django webserver ================================================= [r...@sun]# lsof -P -i -n |grep Xvnc Xvnc 3691 bill 0u IPv4 14835 TCP *:6001 (LISTEN) Xvnc 3691 bill 3u IPv4 14371 TCP *:8000 (LISTEN) Xvnc 3691 bill 4u IPv4 14745 TCP 10.1.1.1:8000- >10.1.1.144:52607 (ESTABLISHED) Xvnc 3691 bill 6u IPv4 14838 TCP *:5901 (LISTEN) Xvnc 3691 bill 7u IPv4 14839 TCP *:5801 (LISTEN) ================================================== Development server is running at http://0.0.0.0:8000/ Quit the server with CONTROL-C. Error: That port is already in use. > > Overall, starting VNC from a web application seems like a bad idea > in principle as the request-response cycle is not well suited for this > (as well as other reasons). Can you describe what are you trying to > achieve and why? What am I doing is want to simplify using vnc. I'm a Linux administrator. As you know, if users want to use vnc they must login the server with ssh to start vnc server first. Then get the port or id number, then use vncviewer or http link to access the vncserver. I just want them to access the http link let django start the vncserver and use it. they don't need to install any ssh client. Thanks in advance. Bill -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
