in reply to Beating the system

It's hard to guess. Perhaps either open filehandle counts or locked memory. CGI.pm will load as much of the file as possible into memory (whatever is currently available to a fh->read call) so that might impact your locked memory usage. While I'm no OS programmer I always thought that memory was locked so you do an immediate read/write from it - perhaps you're tying up valuable space with your data. I also spent a minute reading each of your imports to guess at the number of open file handles (not much but perhaps more than you expected) to see if that was the problem.

Counting file handles: low teens. 

1 perl
1 the script
1 DynaLoader.so / .dll
3 CGI.pm
=> Carp.pm
=> Exporter.pm
2 Fcntl.pm
=> Fcntl.so / .dll
1 File/Basename.pm
? I don't know whether to count STDIN/STDOUT.
1 The file opened on disk for storing the uploaded file.

Replies are listed 'Best First'.
Re^2: Beating the system
by Aristotle (Chancellor) on Sep 29, 2002 at 15:57 UTC
    It doesn't make sense that there would be enough filehandles when files uploaded are under 35kb though.

    Makeshifts last the longest.

[reply]

      I think you meant "wouldn't". Anyhow yeah, that's what counting lead me to believe but I didn't want to throw away that work either ;-) I figured that maybe someone else might be interested in all the other stuff that gets opened up as well.

[reply]
        I meant "would", because I said "under 35kb", in which case, as the original poster says, files upload correctly. It doesn't make sense that he hits a filehandle limit for large but not small files.

        Makeshifts last the longest.

[reply]

In Section Seekers of Perl Wisdom