in reply to Remote Session Starting

How are you exporting the display? If you're using an X server on your windows machine, I would guess you won't be able to do anything useful with Win32::GUITest (except maybe close and move windows around, if your X server doesn't run in a single window). But I may be mistaken. I haven't tried that.

Anyway, why would you end the session? As far as I can tell, you can just keep the session around while working with Win32::GUITest or whatever you want, and close the session when you're done. Or are you running some program that just immediately ends? If so, you should examine the docs for that program to see how to keep it running.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Replies are listed 'Best First'.
Re^2: Remote Session Starting
by Anonymous Monk on Feb 28, 2008 at 22:51 UTC
    So here is some of the code to do the exporting of the session, I am using Net::Telnet to get to the Unix Server:


    my($session);
    $session = new Net::Telnet
    (
    Timeout => 10,
    Prompt => $prompt
    );

    $session -> input_log($logFileName);
    $session -> open($host);
    $session -> login($username, $password);

    $session -> cmd("export DISPLAY=$ADDRNUM:0.0");
    print( STDOUT "Starting X-Motif GUI xrel in background mode\n" );
    $session -> cmd("xrel&");
    sleep 5;
[reply]
      I am not sure how to operate on the GUI while in $session as the commands in Net::Telnet do not look like what I might need or want.

      If I get rid of the sleep the session goes away.
[reply]
        If I get rid of the sleep the session goes away.
        Erm, that wouldn't be because that's the end of the script, which would close the telnet session and disconnect the programs? Can't you just start your Win32::GuiTest code right where you now have the sleep?

        update: IIRC, if you let the $session variable go out of scope (or otherwise overwrite it) that would close the session too. As far as I can see, you only have to make sure the $session variable (and with it, the session) is kept as is while you carry out whatever tasks you need.

        update2: s/$telnet/$session/

        "What should it profit a man, if he should win a flame war, yet lose his cool?"
[reply]

In Section Seekers of Perl Wisdom