msa@rwing.UUCP (Mark Anacker) (07/15/89)
[] Hello out there in HP land.... Can any of you networking guru's tell me if there is a limit to the number of simultaneous sockets available under HP/UX? Say, something like "64 per process, up to 256 per system" or something like that. This is one of those little problems that you just know there must be an answer to, but don't know who to ask. Please reply to msa@toybox (...!rwing!toybox!msa) to save the net. Or post it if you think the answer is generally useful. (How many people want that many TCP connections open at once anyway?) Thanks. -- Mark Anacker, Seattle WA msa@toybox -or- msa@rwing "...I'd like to lie, shipwrecked and comatose, drinking fresh mango juice..." - theme from Red Dwarf
billg@hpindda.HP.COM (Bill Gilbert) (07/26/89)
>Can any of you networking guru's tell me if there is a limit to the number >of simultaneous sockets available under HP/UX? Say, something like >"64 per process, up to 256 per system" or something like that. The key is that sockets are just flavors of files. When you create a socket you use up a file descriptor. When you run out of file descriptors you cannot create more sockets. So the question is: how may file descriptors are available to a process? Bill (I don't know the answer but I know the right question) Gilbert
marden@hpcupt1.HP.COM (Jennifer Marden) (07/26/89)
Currently HP-UX limits each process to 60 file descriptors, so the most sockets a process can have at any one time would be 60. Jennifer Marden
ted@hpwrce.HP.COM ( Ted Johnson) (07/27/89)
>cannot create more sockets. So the question is: how may file descriptors >are available to a process? With 6.5 (and I believe 3.1) the limit is 60 (NFILE). -Ted
rodc@hpfcmgw.HP.COM (Rod Cerkoney) (07/27/89)
Presently there is a 60file/process limit. This is 'hardcoded' into the kernel and not configurable.
rodc@hpfcmgw.HP.COM (Rod Cerkoney) (07/28/89)
Ted sez: >With 6.5 (and I believe 3.1) the limit is 60 (NFILE). Actually NFILE is the total number of files open for the entire system. See Appendix D of the Sys Admin manual. From /usr/include/sys/param.h: #define NOFILE 60 /* max open files per process */ I have been told that if this is changed other things will break. Sorry I but I don't know what those 'other things are'. (My comments relate only to the Series 300) > -Ted > ---------- Rod ( Just the facts ma'am ) Cerkoney.
daveh@hpubvwa.HP.COM (Dave Highley) (07/28/89)
The number 60 comes to mind as the maximum number of open files per process.
ted@hpwrce.HP.COM ( Ted Johnson) (07/30/89)
>Ted sez: > >>With 6.5 (and I believe 3.1) the limit is 60 (NFILE). > > > Actually NFILE is the total number of files open for the entire system. > See Appendix D of the Sys Admin manual. > > > From /usr/include/sys/param.h: > > #define NOFILE 60 /* max open files per process */ Thanks for the correction. I guess maybe I should have bought a vowel.... :-) -Ted
ptc@hpgnd.HP.COM (Paul T.CONGDON) (07/31/89)
There is also a limitation on the number of open sockets you can process through the 'select' system call. I believe this limit is 64. Paul Congdon
rclark@speclab.bgp-usgs.gov (Roger N. Clark) (08/02/89)
Could the socket limitation be a problem with X-windows terminals? What if you have an series 800 serving 10 or 20 X-windows terminals (I am planning 5 in the next year, and a few more after that)? What limitations could be encountered, and is HP thinking/planning to change those limits for this very problem? Roger N. Clark ..!speclab!rclark
stroyan@hpfcdc.HP.COM (Mike Stroyan) (08/08/89)
> Could the socket limitation be a problem with X-windows terminals? > What if you have an series 800 serving 10 or 20 X-windows terminals > (I am planning 5 in the next year, and a few more after that)? What > limitations could be encountered, and is HP thinking/planning to > change those limits for this very problem? > Roger N. Clark The limit on open file descriptors has no impact on using X11 terminals. The limit affects how many client connections an X11 server process can have. With an X11 terminal the terminal plays the role of an X11 server instead of the server being a process on the host computer. Because an X11 terminal user tends to run different programs than a normal terminal user, the host computer may need more of configurable resources such as ptys, swap space, and processes. Each client program started by a person using an X11 terminal will use at least one process. Each terminal emulator window will use a pty device. Mike Stroyan, stroyan@hpfcla.hp.com
harry@hpcvlx.HP.COM (Harry Phinney) (08/08/89)
> Could the socket limitation be a problem with X-windows terminals? > Roger N. Clark It shouldn't be. The socket limit is per-process, not per-user or per-login. Each X client typically only uses one socket connection to the server. The limit is more apparent running the X server on the HP-UX machine (as opposed to on a terminal), where one will be limited to around 60 client connections. Harry Phinney
marden@hpcupt1.HP.COM (Jennifer Marden) (08/08/89)
The socket limit is a per process limit, so as long as you don't have a single process which needs more than 60 open sockets (and/or files), there is no problem. Jennifer Marden