Rajee> I am using straps/scotty in a Tcl based application to
Rajee> create/connect sockets for networking functions.
Rajee> When I execute my bridge I get the following error:
Rajee> "Fatal internal error: straps unable to connect socket broken pipe" and
Rajee> my process is killed but
Rajee> straps is still running. Is this problem due to Unix file system
Rajee> problems or due to additional
Rajee> configurations needed in using straps. Can someone help me out?
Hmm, I could not find this error message in the scotty 2.1.7 sources.
Maybe it's garbled by mixed stdout/stderr channels, but i found
nothing appropriate.
Maybe you can help us with a description of your platform and the
version of scotty you use.
A wild guess:
If you are running this on a Solaris platform, it may be the SIGPIPE
signal delivered, after a ECONNREFUSED is returned by a connect call
to a unix-socket.
Then you should follow the manpage and close the socket and rego (or
the tnm extension should do this ;-).
However, the better solution would be to increase the backlog of the
listen call in straps itself.
But this is a guess and it maybe completely wrong.
Erik
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.