Sponsored Content
Full Discussion: Strange memory behavior
Operating Systems AIX Strange memory behavior Post 302723681 by DGPickett on Tuesday 30th of October 2012 02:20:30 PM
Old 10-30-2012
Used to call it wired. In MULTICS, temp files could be created with no backing store, so they were de facto wired. You could bring a sysem to its knees with too much, but it was great for stress testing the apps.

Closed files with not buf sounds like pipes and sockets in a would-block state, possibly with a blocked thread but perhaps just not firing bits into select() or poll(). If they are accumulating, there may be something undermining keepalive for detecting broken connections, or some privileged app leaving sockets open. lsof can tell you about all open fd.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

strange sed behavior

I have a file called products.kp which contains, for example, 12345678,1^M 87654321,2^M 13579123,3 when I run the command cat products.kp| sed -f kp.sed where kp.sed contains s,^M,, I get the output 12345678,1 87654321,2 13579123,3 (5 Replies)
Discussion started by: Kevin Pryke
5 Replies

2. UNIX for Dummies Questions & Answers

Strange Behavior on COM2

Hi, I have a problem with a new touch screen controller that I am trying to use on a SCO 3.0 system. THe touch screen controller only wants to talk at 9600baud. I have updated /etc/inittab per the manual and also edited /usr/lib/event/devices to use 9600 baud. The only way I can get the... (0 Replies)
Discussion started by: Elwood51
0 Replies

3. AIX

Strange Real Memory usage behavior

We have 2 Rs6000 S-85 Each initially had/have 6 processors and 8 GIG of RAM each Node 1 we added 14 processors and 32 GIG of RAM On May 19. (11 days ago) My memory utilization reporting for node 1 showed a spike in available memory 25-30GB for May 19 to 25 . I kind of expected this because I... (5 Replies)
Discussion started by: Skyybugg
5 Replies

4. Shell Programming and Scripting

Very Strange Behavior for redirection

I have searched far and wide for an explanation for some odd behavior for output redirection and haven't come up with anything. A co-worker was working on old scripts which have run for years and embedded in their code were output redirects which worked for the script during execution and then... (5 Replies)
Discussion started by: cahook
5 Replies

5. Shell Programming and Scripting

nawk strange behavior

Dear guys; when deleting repeated lines using nawk as below ; Why the below syntax works? nawk ' !a++' infile > outfile and when using the other below syntax the nawk doesn't work? nawk ' { !a++ } ' infile > outfile or nawk ' { !a++ } ' infile > outfile BR (4 Replies)
Discussion started by: ahmad.diab
4 Replies

6. Programming

Strange behavior in C++

I have the following program: int main(int argc, char** argv){ unsigned long int mean=0; for(int i=1;i<10;i++){ mean+=poisson(12); cout<<mean<<endl; } cout<<"Sum of poisson: "<< mean; return 0; } when I run it, I get the... (4 Replies)
Discussion started by: santiagorf
4 Replies

7. Ubuntu

Ubuntu strange behavior

It is so till login screen. I mean that when I boot my computer, Ubuntu shows a splash screen with mouse instead of Ubuntu logo and in the login screen it shows XUbuntu login screen... It began when I upgraded to previous kernel, I suppose, but I'm not sure... I can't say that it annoys me very... (6 Replies)
Discussion started by: Sapfeer
6 Replies

8. AIX

Strange behavior with tar

I am trying to create an archive using tar. I am specifying a list of directories using the -L option. For testing purposes I created a simple directory structure: /backup/test /backup/test/test1 /backup/test/test2 The file specified by the -L option, named files.txt, contains:... (8 Replies)
Discussion started by: judykstra
8 Replies

9. Shell Programming and Scripting

Strange Ctrl+C behavior

Hello All, I have a strange issue. I've created a shell script which connects to RMAN (Oracle Recovery Manager) and executes full DB backup. I then executed this script with nohup and in the background: $ nohup my_script.sh > logfile.log 2>&1 &The issue is that when I tried to take a look into... (6 Replies)
Discussion started by: JackK
6 Replies
select(2)							System Calls Manual							 select(2)

NAME
select(), pselect(), FD_CLR(), FD_ISSET(), FD_SET(), FD_ZERO() - synchronous I/O multiplexing SYNOPSIS
For Backward Compatibility Only: (_XOPEN_SOURCE_EXTENDED not defined) DESCRIPTION
The and functions indicate which of the specified file descriptors is ready for reading, ready for writing, or has an error condition pend- ing. If the specified condition is false for all of the specified file descriptors, and block, up to the specified timeout interval, until the specified condition is true for at least one of the specified file descriptors. The and functions support regular files, terminal and pseudo-terminal devices, STREAMS-based files, FIFOs and pipes. The behaviour of and on file descriptors that refer to other file types is unspecified. The nfds argument specifies the range of file descriptors to be tested. The and functions test file descriptors in the range of 0 to nfds -1. File descriptor f is represented by the bit 1<<f in the masks. More formally, a file descriptor is represented by: If the readfds argument is not a null pointer, it points to an object of type fd_set that on input specifies the file descriptors to be checked for being ready to read, and on output indicates which file descriptors are ready to read. If the writefds argument is not a null pointer, it points to an object of type fd_set that on input specifies the file descriptors to be checked for being ready to write, and on output indicates which file descriptors are ready to write. If the errorfds argument is not a null pointer, it points to an object of type fd_set that on input specifies the file descriptors to be checked for error conditions pending, and on output indicates which file descriptors have error conditions pending. On successful completion, the objects pointed to by the readfds, writefds, and errorfds arguments are modified to indicate which file descriptors are ready for reading, ready for writing, or have an error condition pending, respectively. For each file descriptor less than nfds, the corresponding bit will be set on successful completion if it was set on input and the associated condition is true for that file descriptor. If the timeout argument is not a null pointer, it specifies a maximum interval to wait for the selection to complete. The timeout argument points to an object of type for and to an object of type for If the members of these structures are 0, or will not block. If the timeout argument is a null pointer, or will block until an event causes one of the masks to be returned with a valid (non-zero) value. If the time limit expires before any event occurs that would cause one of the masks to be set to a non-zero value, or completes successfully and returns 0. Implementations may place limitations on the maximum timeout interval supported. On all implementations, the maximum timeout interval sup- ported will be at least 31 days. If the timeout argument specifies a timeout interval greater than the implementation-dependent maximum value, the maximum value will be used as the actual timeout value. Implementations may also place limitations on the granularity of time- out intervals. If the requested timeout interval requires a finer granularity than the implementation supports, the actual timeout inter- val will be rounded up to the next supported value. If sigmask is not a null pointer, then the function shall replace the signal mask of the process by the set of signals pointed to by sig- mask before examining the descriptors, and shall restore the signal mask of the process before returning. If the readfds, writefds, and errorfds arguments are all null pointers and the timeout argument is not a null pointer, or blocks for the time specified, or until interrupted by a signal. If the readfds, writefds, and errorfds arguments are all null pointers and the timeout argument is a null pointer, or blocks until interrupted by a signal. File descriptors associated with regular files always select true for ready to read, ready to write, and error conditions. On failure, the objects pointed to by the readfds, writefds, and errorfds arguments are not modified. If the timeout interval expires without the specified condition being true for any of the specified file descriptors, the objects pointed to by the readfds, writefds, and errorfds arguments have all bits set to 0. Ttys and sockets are ready for reading if a would not block for one or more of the following reasons: o input data is available. o an error condition exists, such as a broken pipe, no carrier, or a lost connection. Similarly, ttys and sockets are ready for writing if a would not block for one or more of the following reasons: o output data can be accepted. o an error condition exists, such as a broken pipe, no carrier, or a lost connection. TCP sockets select true on reads only for normal data. They do not select true on reads if out-of-band data ("urgent" data) arrives. TCP sockets select true on exceptions for out-of-band data. AF_CCITT sockets select true on reads for normal and out-of-band data and information, including supervisory frames. Pipes are ready for reading if there is any data in the pipe, or if there are no writers left for the pipe. Pipes are ready for writing if there is room for more data in the pipe AND there are one or more readers for the pipe, OR there are no readers left for the pipe. returns the same results for a pipe whether a file descriptor associated with the read-only end or the write-only end of the pipe is used, since both file descriptors refer to the same underlying pipe. So a of a read-only file descriptor that is associated with a pipe can return ready to write, even though that particular file descriptor cannot be written to. File descriptor masks of type fd_set can be initialized and tested with and It is unspecified whether each of these is a macro or a func- tion. If a macro definition is suppressed in order to access an actual function, or a program defines an external identifier with any of these names, the behaviour is undefined. Clears the bit for the file descriptor fd in the file descriptor set fdset. Returns a non-zero value if the bit for the file descriptor fd is set in the file descriptor set pointed to by fdset, and 0 otherwise. Sets the bit for the file descriptor fd in the file descriptor set fdset. Initializes the file descriptor set fdset to have zero bits for all file descriptors. The behaviour of these macros is undefined if the fd argument is less than 0 or greater than or equal to The use of a timeout does not affect any pending timers set up by or On successful completion, the object pointed to by the timeout argument of may be modified. The is used in the definition of structure. It is set to a value of 2048 to accommodate 2048 file descriptors. Any user code that uses or the structure should redefine to a smaller value (greater than or equal to the number of open files the process will have) in order to save space and execution time. Similarly, any user code that wants to test more than 2048 file descriptors should redefine to the required higher value. The user can also allocate the space for structure dynamically, depending upon the number of file descriptors to be tested. The following code segment illustrates the basic concepts. RETURN VALUE
and return no value. returns a non-zero value if the bit for the file descriptor fd is set in the file descriptor set pointed to by fdset, and 0 otherwise. On successful completion, and return the total number of bits set in the bit masks. Otherwise, -1 is returned, and is set to indicate the error. ERRORS
Under the following conditions, and fail and set to: One or more of the file descriptor sets specified a file descriptor that is not a valid open file descriptor. This could happen either if the file descriptor sets are not initialized or nfds argument is greater than The function was interrupted before any of the selected events occurred and before the timeout interval expired. If has been set for the interrupting signal, it is imple- mentation-dependent whether the function restarts or returns with One or more of the pointers was invalid. The reliable detection of this error is implementation dependent. An invalid timeout interval was specified. Valid values for the number of nanoseconds (in should be a non-negative integer less than 1,000,000,000. For the number of microseconds (in struct timeval), a non-negative integer less than 1,000,000 should be used. Seconds should be specified using a non-negative integer. The nfds argument is less than 0, or is greater than or equal to the value of which specifies the absolute maximum number of files a process can have open at one time. If the resource limit for a process is less than or equal to 2048, is considered to be 2048. One of the specified file descriptors refers to a STREAM or multiplexer that is linked (directly or indirectly) downstream from a multiplexer. EXAMPLES
The following call to checks if any of 4 terminals are ready for reading. times out after 5 seconds if no terminals are ready for reading. Note that the code for opening the terminals or reading from the terminals is not shown in this example. Also, note that this example must be modified if the calling process has more than 32 file descriptors open. Following this first example is an example of select with more than 32 file descriptors. The following example is the same as the previous example, except that it works for more than 32 open files. Definitions for and are in WARNINGS
The file descriptor masks are always modified on return, even if the call returns as the result of a timeout. DEPENDENCIES
supports the following devices and file types: o pipes o fifo special files (named pipes) o all serial devices o All ITEs (internal terminal emulators) and HP-HIL input devices o lan(7) special files o pty(7) special files o sockets AUTHOR
was developed by HP and the University of California, Berkeley. SEE ALSO
fcntl(2), poll(2), read(2), sigprocmask(2), write(2), thread_safety(5), select(2)
All times are GMT -4. The time now is 06:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy