File Limitations

File Limitations

Post by Le » Wed, 14 Aug 1996 04:00:00



Someone keeps telling me that there is a limit to the number of files
that SCO can have open, at one time, and otherwise the system will
crash.  Any experience in this area?

 
 
 

File Limitations

Post by Jean-Pierre Radl » Wed, 14 Aug 1996 04:00:00


Quote:Lee writes:
> Someone keeps telling me that there is a limit to the number of files
> that SCO can have open, at one time, and otherwise the system will
> crash.  Any experience in this area?

Sure enough, run configure and discover MAX-FILE.

--


 
 
 

File Limitations

Post by Bela Lubki » Thu, 15 Aug 1996 04:00:00



> Someone keeps telling me that there is a limit to the number of files
> that SCO can have open, at one time, and otherwise the system will
> crash.  Any experience in this area?

Just guessing, but I would guess SCO has on the order of 200000 files
open right now (~100-200 per employee, between all the desktop systems,
servers, routers etc.).

SCO is a company.

SCO sells three or four major lines of Unix operating system software
(depending whether you count ODT 3-and-earlier and OpenServer 5 as one
or two lines).  Each operating system has different characteristics.
For instance, Xenix and ODT 3-and-earlier have a kernel parameter
controlling how many files can be open at once, system-wide.  OSR5
adjusts this dynamically, as (I believe) does UnixWare.

There are also per-process file limits.  The upper boundary for this
(the most files a single process may open) is 11000 on ODT3 and OSR5.
It's much smaller (less than 300) on older releases of ODT and Xenix.  I
don't know about UnixWare.  The limit can be adjusted on a per-process
basis, on OSR5 and UnixWare.

If the system-wide file limit is exceeded, you will get kernel warning
messages and processes will fail to open files.  If a process exceeds
its per-process limit it will also fail to open files.  The system will
not crash (though it's possible that important system processes will be
adversely affected).

Quote:>Bela<

 
 
 

1. File limitations to 2 GB and driver special files

Hello,

I actually writting a driver for a specific board for Solaris 2.5.1.
I use a character based driver, with a read entry point. When I am
reading on this device, the system generates a EINVAL sys error when the
2 GB limits is reached while reading. In this case, my read entry point
is not called by the read system call. The problem appears when I have
acquired 2 giga bytes of data.

The problem comes from the offset in the file descriptor. I know I could
use a 64 bits offset value instead of a 32 bits by setting the flag
D_64BITS in the cb_flags of my cb_ops structure but this is not a good
solution for me. I consider I should be able to read indefinitivly data
on my device without having such a problem.

I'd like to know what should I do to remove the offset managment for my
driver.

Please, send response to both newsgroup and mail.

Thanks

Gael MARTIN
Enertec


2. Porting FAQs

3. Solaris 7 Directory and File Limitations?

4. ppd (postscript printer driver) help??

5. 2GB File limitation

6. Turn off SCSI-drives?

7. passwd file limitation

8. Unix - Frequently Asked Questions (6/7) [Frequent posting]

9. NFS File Limitation

10. 2GB file limitation

11. going beyond Linux 2Gb file limitation

12. Solaris-Apache: a log files limitation?

13. open file limitations under OpenBSD 2.8