"Craig A. Berry" <[EMAIL PROTECTED]> writes:
> In the last few days I've accumulated the following files in my login
> directory:
>
> $ dir/grand sys$login:perlpipe_*.com
>
> Grand total of 1 directory, 467 files.
>
> Is there a mechanism for automatically cleaning these up that is
> broken, or are we planning to leave a new file in sys$scratch every
> time Perl opens a pipe?
Let me guess, you were running the test suite, right?
The perlpipe_*.com files are only created when Perl can't find
VMSPIPE.COM in any of the "normal" places, and that most commonly
occurs in the test suite where PERL_ROOT isn't defined.
The perlpipe_*.com files should be "self-deleting" (i.e, they figure
out their own name from F$env("PROCEDURE") and then delete themselves)
however if the command being run by perlpipe dies, then the deletion
might not happen.
There may also be protection issues that keep the perlpipe files from
deleting themselves.
--
Drexel University \V --Chuck Lane
----------------->--------*------------<[EMAIL PROTECTED]
(215) 895-1545 / \ Particle Physics [EMAIL PROTECTED]
FAX: (215) 895-5934 /~~~~~~~~~~~ [EMAIL PROTECTED]
