in reply to Re: Killing subprocess in windows
in thread Killing subprocess in windows

> what's the problem?

getting the PID for killing. The file is locked as long as it is open, hence I can check that it was closed.

> surely one can implement

I thought about it, but getting the PID is always helpful.

And I didn't want to fiddle much with stat and seek to read the newest portion of the file plus the idiosyncrasies of Win OS when applying a Unix-born language.

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery

Replies are listed 'Best First'.
Re^3: Killing subprocess in windows
by Marshall (Canon) on May 20, 2021 at 22:12 UTC
    I will admit that I am confused. I just don't understand the basic problem that you have. Could you write a few sentences that describe that? BTW..ich kann deutsch.

    I am just looking for some words that will help me understand what the problem is.

[reply]
      there are log files showing the output from STDOUT and STDERR from some processes, not necessarily Perl processes.

      I need to display each "active" logfile in a dir in a dedicated window which updates automatically.

      This is done with tail -f FILE on Unix, get-content -wait does the analogue on Win

      start opens a new "terminal" in parallel for the output.

      I don't really know the PID of the process writing to the logfile.

      Everything works fine so far, I just need to close the output windows once the logfile is closed. There are hundreds of jobs writing logfiles, I only need to show the active ones.

      That's why I need the PID to be able to kill the process reading from a logfile.

      > BTW..ich kann deutsch.

      fascinating! :)

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      Wikisyntax for the Monastery

[reply]
[d/l]
[select]
        Dein Englisch ist viel besser als mein Deutsch. Ich wollte nur eine Antwort provozieren. OK. Jetzt muss ich darüber nachdenken.
[reply]

In Section Seekers of Perl Wisdom