Max Neupert wrote: > hi list, > > i have the problem that after a crash or just a reopen of a patch > with the netserver object (i believe netreceive will have the same > issue) i need to wait a couple of seconds up to a minute until pd > allows me to open the same patch with a successful creation of the > netserver object, because the port seems to be already (still) in use. > > is there a way to force the port to reset or close? it's a little > annoying especially in live situations if everybody has to wait.... > > m..
---8<--- The problem is related to the fact that "close()" does not ends the connection UNTIL the last of the file descriptors refering to the socket is closed. If other process has a copy of the file descriptor then it doesn't matter if you close your copy, the other copies MUST be closed in order for the socket to be really closed... ---8<--- http://developerweb.net/forum/archive/index.php/t-3480.html Not sure what the solution is, though. It's certainly not a trivial problem to solve. If you can set up the clients to periodically ping the netserver and if there is no reply then disconnect, that might help. _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
