in reply to kill a child / parent process

I refrained from suggesting this yesterday as it looked like you didn't have access to the source for application.exe, but as it appears that you do, how about simply adding 'write-to-a-daily-rotated-log-filename' routine to application.exe instead, rather than having to write more-and-more complicated external control routines? I realise this may be not what you want for other reasons, but it sounds like this is becoming a bit of a monster <g>. Or of course, you could switch to 'nix... :)

Cheers
Ben

Replies are listed 'Best First'.
Re: Re: kill a child / parent process
by ThorstenHirsch (Novice) on Apr 10, 2003 at 12:27 UTC
    Hi Ben,

    well, of course you're right. The thing is, that I'm a trainee and I'm only working in this department of my company for 5 weeks...tomorrow will be the last day ;-)

    At the beginning, I was told, that I should rewrite a korn shell script into something for Windows. I always wanted to learn Perl, so I thought, this might be a good chance.
    From time to time, the professionals here asked me, if i could implement this and that in my script and I was glad of having chosen Perl, but meanwhile there is so much, my script shall do, that I also think it would have been better to edit the application.exe, but it's written in C++.

    For this afternoon, I think I'll give the process creation with Win32::Process another try, but if it doesn't work, I don't mind too much. My script is starting application.exe very well, handles logfiles, links some server shares and monitors them...there's really only the problem with shutting it all down left.


    Bye.
    Thorsten
[reply]
      Nice work! Maybe you can persuade the 'professionals' to let you rewrite application.exe in perl for them - or give them some training...:)

      Cheers
      Ben
[reply]

In Section Seekers of Perl Wisdom