As Dossy says, set your recvwait. Else, it defaults to socktimeout,
which defaults to 30 sec. But, given what you had shown, I'd expect to
see a message in the server log on a recieve timeout (readtimeoutlogging
== true). If you don't see that message in the log, check that you are
running a server version which supports this (4.0.3), or maybe your
config section is not set to the servername/module for the driver that's
being run. Is this not from a nssock module?
Mark
Dossy wrote on 6/3/2004, 8:42 PM:
> On 2004.06.03, Ross Simpson <[EMAIL PROTECTED]> wrote:
> > Just for fun, I started a truss before I submitted the upload form.
> > The file was a 10mb chunk of /dev/random.
>
> truss means Solaris and not Linux -- okay, now that we've established
> this ...
>
> > Snippet: [snip]
> >
> > There were quite a few read()s like those above.
> > When I hit 'Upload', the browser (galeon) showed that it was
> > transferring data to the host. It got as far as 1125k before it
> stalled
> > out. At that same time, the reads stopped in the truss. Galeon's
> still
> > spinng, but stopped at 1125k.
>
> Sounds like the limit is still 1MB.
>
> > Looks like it gave up sending or receiving, for some reason.
> >
> > Here's the relevant part of config.tcl:
> >
> > ns_section "ns/server/${servername}/module/nssock"
> > ns_param maxinput [expr 1024 * 1024 * 100]
> > ns_param readtimeoutlogging true
> > ns_param serverrejectlogging true
> > ns_param sockerrorlogging true
> > ns_param sockshuterrorlogging true
>
> I notice you don't have "recvwait" set (according to this snippet).
>
> ns_param recvwait [expr 15 * 60]
>
> Try that first. If it doesn't make a difference, we'll take the next
> steps. It still feels like maxinput isn't being set to 100MB and it's
> still the 1MB default ... it might help to see the whole config.tcl.
>
> -- Dossy
>
> --
> Dossy Shiobara mail: [EMAIL PROTECTED]
> Panoptic Computer Network web: http://www.panoptic.com/
> "He realized the fastest way to change is to laugh at your own
> folly -- then you can let go and quickly move on." (p. 70)
>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to
> <[EMAIL PROTECTED]> with the
> body of "SIGNOFF AOLSERVER" in the email message. You can leave the
> Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
