Quick Help with File Resource limits on snapshot build

[Jake Janovetz]

It's a shame Microsoft doesn't think this way...  (good for me, 
though..  256 meg is about $100 now!)

   Jake


On Thu, Dec 07, 2000 at 12:26:36PM -0600, Joel Sherrill wrote:
> Jake Janovetz wrote:
> > 
> > Yes, this is a funny little error that popped up at some point.
> > They reduced the default number of file descriptors from like
> > 20 to 3.  That prevents the network from initializing.  So,
> > put this in your init.c:
> > 
> > #define CONFIGURE_LIBIO_MAXIMUM_FILE_DESCRIPTORS   30
> 
> Each file descriptor consumes some memory for structures 
> and a semaphore.  With a default of 20, this was a waste of
> a noticeable amount of memory for most applications.
> 
> The shift in configuration defaults was to minimize RAM
> waste in applications.   :)
> 
> 
> >     Cheers,
> >     Jake
> > 
> > On Thu, Dec 07, 2000 at 04:37:01PM -0000, bob wrote:
> > > Apologies to all for my ignorance. I have just about ported the latest
> > > snapshot to our 68360 BSP but now I get the following errors when RTEMS is
> > > starting up after building any net application (such as the Beta 3 netdemo
> > > example program):-
> > >
> > > Can't bring scc1 up: Too many open files in system
> > > Can't set default route: No such process
> > > No routes!
> > > Create socket.
> > > RTEMS: Can't create socket: Too many open files in system
> > > RTEMS: fatal error, exiting
> > >
> > > I guess I need to allocate some file descriptor resources - I have just
> > > downloaded the IMFS manual but not read it yet (that's homework for
> > > tonight).
> > > Any quick help much appreciated :)
> > > Bob Wisdom
> 
> -- 
> Joel Sherrill, Ph.D.             Director of Research & Development
> joel at OARcorp.com                 On-Line Applications Research
> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>    Support Available             (256) 722-9985