I figured it out all by myself ;-)

#!/usr/pkg/bin/perl -w
# Copyright 2005 by Gan Uesli Starling
# XML-RPC server update script written in Perl.
# For use with this XML-RPC Client/Server pair:
# 1. gus_xml-rpc_server.pl
# 2. gus_xml-rpc_client_tk.pl

# HOW IT WORKS:
# On command, the running server updates itself as follows:
# 1. Receives new version of own script from XML-RPC client.
# 2. Over-writes own script with new version.
# 3. Launches this script in manner similar to below.
# 4. Dies when this script kills it.
# 5. Is reborn when new version launched by this script.

# Args sent by the to-be-restarted, still-running server.
my ( $script_path, $script_list, $local_port, 
     $crypt_key, $plain_pw, $prefork_pid ) = @ARGV;
            
# Lay running server to rest.
kill 15, $prefork_pid; sleep 5; # Gently persuade at first.
kill  2, $prefork_pid; sleep 5; # If ignored, insist harder.
kill  9, $prefork_pid; sleep 5; # If still ignored, use hammer.

# Launch-string for use with 'Process::Create' on Win32.
my $win32_cmd = "perl $script_path/gus_xml-rpc_server.pl "
    . "--script_list $script_list "
    . "--local_port $local_port "
    . "--crypt_key $crypt_key "
    . "--password $plain_pw "
    . "--gui 0 ";

# Launch-array for use with 'fork' on Unix.
my @unix_cmd = (
    "perl", "$script_path/gus_xml-rpc_server.pl", 
    "--script_list", "$script_list",
    "--local_port", "$local_port",
    "--crypt_key", "$crypt_key",
    "--password", "$plain_pw",
    "--gui", "0"
);

# Launch new process the UNIX way.
sub unix_fork_process {
    if ( defined( my $kid = fork ) ) {
        unless ($kid) { 
            exec(@_) or die "Oops! Cannot exec.";
        }
    }
}

# Launch new process the Win32 way.

sub win32_create_process {
    my $win32_cmd = shift;
    require Win32::Process;
    require Win32;
    no strict;
    my $obj;

    sub ErrorReport{
        print Win32::FormatMessage( Win32::GetLastError() );
    }
    $win32_cmd =~ s/\//\\/g; # Backslashes for Win32.

    Win32::Process::Create(
        $obj, "C:\\Perl\\bin\\wperl.exe",
        "$win32_cmd", 0, NORMAL_PRIORITY_CLASS, "."
    ) || die ErrorReport();
}

# Launch new process any way whichever...
if ($^O =~ /Win32/i) { win32_create_process($win32_cmd) }
else { unix_fork_process(@unix_cmd) }

[download]

In reply to Re: Socket left open on Win32 after fork-and-die... by aplonis
in thread Socket left open on Win32 after fork-and-die... by aplonis

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.