use Perl

• It's worse than that (Score:1)

  by Dom2 (2981)

  Have a look at the code. I seem to recall that those numbers don't mean what you think that they mean...

  From /usr/src/linux/Documentation/sysctl/fs.txt:

  The kernel allocates file handles dynamically, but as yet it doesn't free them again. The value in file-max denotes the maximum number of file- handles that the Linux kernel will allocate. When you get lots of error messages about running out of file handles, you might want to increase this limit. The three values in file-nr denote the number of alloc
• tempfile (Score:2, Informative)

  by Dom2 (2981)

  I've found tempfile() easiest to work with when you don't specify any parameters. That way, you just get back a filehandle and a name. If you only want a filehandle to play with, it gets even easier as the autodelete should happen automatically when the $fh goes out of scope.

  What happens if you put a close $fh in there before you leave the routine?

  -Dom
  • Re:tempfile (Score:2)

    by ajt (2546)

    Dom2,

    Useful comments. I agree it's a great module, the problem started when I was working with it on NT and Linux. When I'd finished NT was working okay, but Linux was not....

    If you have an explicit close $fh, then what I found was that the file was NOT deleted, and I can't remember if the file handle was. I've even tried an explicit unlink too.

    Like I said I feel part of the problem is that it's running under mod_perl PerlRun, which is a bit of an odd place!

    Since I posted, I'm now at: 8192, 2781, 16

    --
    -- "It's not magic, it's work..."
    • Re:tempfile (Score:1)

      by Dom2 (2981)

      As I said in the first reply, I don't necessarily think those kernel figures are anything to worry about. But I would be concerned about the undeleted files.

      The docs state that a file is not auto deleted, if a filehandle is requested as well as a filename. You have to unlink it yourself.

      One more thing; You might wish to check whether or not the unlink fails: unlink( $fname ) or warn "unlink($fname): $!\n"

      Oh, and to see whether filehandles are leaking in real, useful terms, the best thing to do is r
      • Re:tempfile (Score:2)

        by ajt (2546)

        Dom,

        I think I know what is going on! I created the following little script, popped it into my PerlRun folder on my home Linux box and tested all the permutations.

        #!/usr/bin/perl
        $|++;
        
        use strict;
        use CGI;
        use File::Temp qw(tempfile unlink0);
        
        my $q = CGI->new;
        
        print $q->header(-type => "text/plain");
        
        print "PID: $$\n";
        print `cat /proc/sys/fs/file-nr`;
        
        for (1..50) {
            my ($TMP_FH, $tmp_file) = tempfile(SUFFIX => ".f", UNLINK => 0);
            print "Created: $tmp_file\t";
         

        --
        -- "It's not magic, it's work..."