03-18-2012
18-Mar-2012 14:25:03.209 general: error: socket: file descriptor exceeds limit (4096/4096)
I have BIND 9.8.1-P1 cache only DNS server running in Solaris 10. I have upgraded the same from 9.6.1 to 9.8.1-P1. Now i am facing "file descriptor exceeds limit (4096/4096)" error frequently on the server.
Please help me on this issue!
Last edited by DukeNuke2; 03-18-2012 at 01:52 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am trying to write a script to Count Files in a directory located on a remote server and send an email Notification if it exceeds a limit. The code given below doesnot check the condition and sends the mail everytime irrespective of the condition. I have put this script in the cron. Can... (10 Replies)
Discussion started by: amitsayshii
10 Replies
2. Shell Programming and Scripting
Hi EveryOne
We run CICS Sofware on our AIX Machine...
When ever some Process or Transaction loops it Takes heavy process Usage..
Is there a way that i can Get a alert message or a Message Thrown on to screen when ever a process named "cicsas" uses more that 20%... fo CPU..
I was... (4 Replies)
Discussion started by: pbsrinivas
4 Replies
3. IP Networking
Hi Friends,
I have written a program which will listener for more than 1000 requests per second from a single socket descriptor and then it will process those requestes. Its taking X amount of time. Now i want to reduce that time. Will I can write multiple threads to receive the... (2 Replies)
Discussion started by: pa.chidhambaram
2 Replies
4. Programming
Hi,
I want to validate that a file is a socket file on Linux. I know I can do this using the S_ISSOCK macro, but I am not sure how to get the file descriptor for the socket file.
For example, I know that /tmp/mapping-foo is a socket file. In Python I can do something like this:
>>> import... (2 Replies)
Discussion started by: goon12
2 Replies
5. UNIX for Dummies Questions & Answers
Everytime I try to start Discreet Flame on my Octane2 machine it keeps giving me an error message "initial log size exceeds limit--aborting"
Can anyone please help me how to fix this problem. Thanks.
Octane2
IRIX64 Release 6.5
Flame 2007 (0 Replies)
Discussion started by: dewaraja
0 Replies
6. UNIX for Advanced & Expert Users
Everytime I try to start Discreet Flame on my Octane2 machine it keeps giving me an error message "initial log size exceeds limit--aborting"
Can anyone please help me how to fix this problem. Thanks.
Octane2
IRIX64 Release 6.5
Flame 2007 (0 Replies)
Discussion started by: dewaraja
0 Replies
7. Shell Programming and Scripting
Everytime I try to start Discreet Flame on my Octane2 machine it keeps giving me an error message "initial log size exceeds limit--aborting"
Can anyone please help me how to fix this problem. Thanks.
Octane2
IRIX64 Release 6.5
Flame 2007 (6 Replies)
Discussion started by: dewaraja
6 Replies
8. Hardware
I have a 320 GB drive which dual boots Windows and Debian:
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal):... (0 Replies)
Discussion started by: phillipsoasis
0 Replies
9. Shell Programming and Scripting
How can i remove a file using shell script when its size exceeds 10MB. Given that file is located in different location to the shell script where it is running? (4 Replies)
Discussion started by: vel4ever
4 Replies
10. Solaris
Hello All,
I am having an issue with ellipse environment,
Subscribing ellipse version /opt/mincom/ellipse/bs037__ora_cics_svr
.profile: ulimit: exceeds allowable limit ,
prj -l ellsupp
#ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192... (22 Replies)
Discussion started by: Revathi2089
22 Replies
PIPE(2) System Calls Manual PIPE(2)
NAME
pipe - create an interprocess channel
SYNOPSIS
pipe(fildes)
int fildes[2];
DESCRIPTION
The pipe system call creates an I/O mechanism called a pipe. The file descriptors returned can be used in read and write operations. When
the pipe is written using the descriptor fildes[1] up to 4096 bytes of data are buffered before the writing process is suspended. A read
using the descriptor fildes[0] will pick up the data. Writes with a count of 4096 bytes or less are atomic; no other process can inter-
sperse data.
It is assumed that after the pipe has been set up, two (or more) cooperating processes (created by subsequent fork calls) will pass data
through the pipe with read and write calls.
The Shell has a syntax to set up a linear array of processes connected by pipes.
Read calls on an empty pipe (no buffered data) with only one end (all write file descriptors closed) returns an end-of-file.
SEE ALSO
sh(1), read(2), write(2), fork(2)
DIAGNOSTICS
The function value zero is returned if the pipe was created; -1 if too many files are already open. A signal is generated if a write on a
pipe with only one end is attempted.
BUGS
Should more than 4096 bytes be necessary in any pipe among a loop of processes, deadlock will occur.
ASSEMBLER
(pipe = 42.)
sys pipe
(read file descriptor in r0)
(write file descriptor in r1)
PIPE(2)