hello max
i was told, that it is not related to pd itself, but to the kernel. when connections are not properly closed, then the kernel sets the specific port into kind of a 'wait for closing'-state. sometimes it takes up to 10 minutes, until the state changes to 'finished', but only then this specific port is freed again and you can create a [netserver] again. (this is a very clumsy explanation, someone with a deeper understanding of how the kernel handels tcp connections could explain that much more adequate). anyway, i think there is no workaround for this on the pd-side, it seems. i had the impression, that in case of a server-crash, it helps, when each connected client closes the connection (read: send a [disconnect(-message to [netclient]), although the connection seems already closed. netpd suffers from this problem as well.
roman
On Tue, 2007-06-05 at 02:50 +0200, 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..
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de