J
Jeremy Slade
I'm running perl 5.6.1 on linux i686 kernel 2.6.8
I had a very strange experience this morning that is rather alarming to
me. I was running a perl script that has been running many hundreds of
times before... I had executed it with the incorrect options, so I hit
Ctrl-C to kill it.
Somehow the result of this is that every file to which I had an open
handle became a unix FIFO on disk -- as though the file was removed,
then mkfifo was run in it's place. e.g. it look like this afterwards:
% ls -lF foo
prw-rw-r-- 1 jgs jgs 0 Feb 15 10:39 foo|
Some file were opened with IO::File->new(), some were opened via perl's
'do' function -- and it least one case was a symlink on a path to an
open file, but not the actual file itself.
Can anyone please explain how this could happen? I check the perl 5.6.1
source code for all occurrences of mkfifo or mknod, I don't see anything
where it is used except in the xs interface stuff, nothing internal.
This is not only baffling, but also alarming that this could happen.
Thanks in advance,
Jeremy
I had a very strange experience this morning that is rather alarming to
me. I was running a perl script that has been running many hundreds of
times before... I had executed it with the incorrect options, so I hit
Ctrl-C to kill it.
Somehow the result of this is that every file to which I had an open
handle became a unix FIFO on disk -- as though the file was removed,
then mkfifo was run in it's place. e.g. it look like this afterwards:
% ls -lF foo
prw-rw-r-- 1 jgs jgs 0 Feb 15 10:39 foo|
Some file were opened with IO::File->new(), some were opened via perl's
'do' function -- and it least one case was a symlink on a path to an
open file, but not the actual file itself.
Can anyone please explain how this could happen? I check the perl 5.6.1
source code for all occurrences of mkfifo or mknod, I don't see anything
where it is used except in the xs interface stuff, nothing internal.
This is not only baffling, but also alarming that this could happen.
Thanks in advance,
Jeremy