in reply to Re^4: Beating the system
in thread Beating the system

Either I'm addled from cleaning dog poo (I was cleaning up a mess just now) and I've forgotten how to read English or you forgot a 'not'. You said that it would not make sense for there to be enough handles if the file size is under 35KB. I'm not sure what quantities of file handles have to do with file size anyway but that's separate. I always thought a single file handle can take any fize file absent any restrictions the OS has.

So... if I'm addled don't bother responding. It won't help.

Replies are listed 'Best First'.
Re^6: Beating the system
by Aristotle (Chancellor) on Sep 29, 2002 at 19:28 UTC
    Exactly your question was mine. Files under 35kb upload perfectly for the poster, larger files don't. As there are sufficient filehandles to upload small files, there must also be enough to upload large ones. Right?

    Makeshifts last the longest.

[reply]

      So... if the problem was locked memory (I think there might be some other restrictions that mkie either doesn't know about or didn't think of) then how would a perl user know that it had been exceeded? I'm hoping that more sysadminly people will know the answer since while this isn't a problem I have - it might happen later since you never know when you're going to end up with a restrictive environment. Some form of signal trapping?

      mikeirw - that's an idea worth trying. Install some signal traps and see if you can find out what's killing your process that way. Check out the perlipc for more details on the how that works. I'm thinking that if you can just do something like $SIG{SOMETHING} = sub { print "SIGSOMETHING triggered" } to minimally instrument your program.

[reply]
[d/l]

In Section Seekers of Perl Wisdom