If it never sends an XML-RPC response back, you may want to close STDIN, STDOUT and maybe other open files after you fork. You can do it in /usr/local/bin/monster but it would be better to do it before you exec(). (You can also set close-on-exec if you know how to do that.)

Well, funnily enough the XML-RPC response occurs correctly. the applet doesn't specifically 'wait' for a response, but the XML-RPC class I'm using seems to want to wait anyway: 

if(mx.getRun()){
                Vector params = new Vector();
                params.add(mx.toString());
                try{
                    client.execute("Monster.go", params);
                    getAppletContext().showDocument(new URL("http://mo
+nster.northwestern.edu/monster.jsp?pji="+id));
                 }
                catch(ConnectException ex){ex.printStackTrace();}
                catch(IOException ex){ex.printStackTrace();}
                catch(XmlRpcException ex){
                    ex.printStackTrace();
                    try{
                        getAppletContext().showDocument(new URL("http:
+//monster.northwestern.edu/monster.jsp?pji="+id));
                    }catch(MalformedURLException exc){exc.printStackTr
+ace();}
                }
            }

[download]
i added the '.showDocument' in the XmlRpcException catch, because it threw if it got a return that was weird, so just knowing that a return happened tells me the 'exec' happened (i hope). adding that catch didnt change a thing about the button hanging.

To answer your question:

Is the program "/usr/local/bin/monster" interacting with the XML-RPC client or does it just go off and do its own thing?

monster does its own thang, the 'return 0' in the daemon IS the final interaction with the XML-RPC client.

i'll have a go at checking where the hanging happens in the daemon, cheers

Sam

In reply to Re: Re: It works, and then it doesn't...connecting to a daemon over the net by seaver
in thread It works, and then it doesn't...connecting to a daemon over the net by seaver

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.