01-28-2016
Do you trink that one process can steal file descriptors from another process??
It cannot. Each process has its own 1024 (or 2048 if set with ulimit) descriptors.
This User Gave Thanks to MadeInGermany For This Post:
10 More Discussions You Might Find Interesting
1. Programming
How can I transfer an open file description between two process? (1 Reply)
Discussion started by: xu_wen_dong
1 Replies
2. UNIX for Dummies Questions & Answers
I have a UNIX daemon process that's been started by a parent process, an application server.
The behavior of this daemon process is to inherit and use the app
server's file descriptors (ports/sockets).
When I shutdown the app server, the daemon continues to run, because there may be other... (1 Reply)
Discussion started by: kunalashar
1 Replies
3. UNIX for Advanced & Expert Users
I have set the maximum no of file descriptors open in a process to the value 8192 using the following lines
set rlim_fd_max=8192
set rlim_fd_cur=8192
in the /etc/system file.
I rebooted the machine and the command ulimit -n / -Hn both display the limits as 8192. However when I run my... (2 Replies)
Discussion started by: lakshmankumar12
2 Replies
4. Shell Programming and Scripting
We have a process that is running out of file handles. Is there some command line way to determine this that we can include into a cron script?
Please let me know
JAK (3 Replies)
Discussion started by: jakSun8
3 Replies
5. Shell Programming and Scripting
hi,
I'm using HP unix tru64 & Win XP.
i'm download a file from winxp to unix using ftp.
how to know whether a remote file is currently being used by the process or not? (my loaction unix server) (7 Replies)
Discussion started by: Tlg13team
7 Replies
6. OS X (Apple)
I am having a client/server application which will download files from server. If server has directories, it will create directories/sub directories and then download files. In this process, I observed that number of open files are more than 400 (which is approxmately same as number of dir/subdir... (1 Reply)
Discussion started by: satyam90
1 Replies
7. Solaris
Hi
want to know what file (descriptor+filename+socket) is being accessed by particular process on solaris.
Purpose : while running perf. test, needs to find where is the bottleneck.
We are providing concurrnet load for around 1 hr and needs to capture data related to file usage pattern... (1 Reply)
Discussion started by: raxitsheth
1 Replies
8. Red Hat
First post, sorry to be a bother but this one has been dogging me. I have a process user (java application server) that trips a resource limit every couple weeks and need help finding what limit we're hitting.
First, this is what's running:
This is the error when jobs are run or the... (0 Replies)
Discussion started by: Katahdin
0 Replies
9. SCO
Hi
How to increase maximum number of open file in "sco xenix binary" running in "sco unix openserver 5.0.7" ?
I have changed "NOFILES" kernel parameter to 512, but xenix binray can't open more than 60.
tnx (4 Replies)
Discussion started by: javad1_maroofi
4 Replies
10. Shell Programming and Scripting
Hi,
I've came across an issue with a script I've been writing to check DHCP addresses on an Solaris system, the script has been running reasonably well, until it hit the following problem:
./sub_mon_v2: redirection error: cannot duplicate fd: Too many open files
./sub_mon_v2: cannot make... (3 Replies)
Discussion started by: CiCa
3 Replies
LEARN ABOUT MOJAVE
filebyproc.d
filebyproc.d(1m) USER COMMANDS filebyproc.d(1m)
NAME
filebyproc.d - snoop opens by process name. Uses DTrace.
SYNOPSIS
filebyproc.d
DESCRIPTION
filebyproc.d is a DTrace OneLiner to print file pathnames as they are opened, including the name of the process calling the open. A line
will be printed regardless of whether the open is actually successful or not.
This is useful to learn which files applications are attempting to open, such as config files, database files, log files, etc.
Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt in the DTraceToolkit contain this as a oneliner that can be cut-n-paste to run.
Since this uses DTrace, only users with root privileges can run this command.
EXAMPLES
This prints new process name and pathnames until Ctrl-C is hit.
# filebyproc.d
FIELDS
CPU The CPU that recieved the event
ID A DTrace probe ID for the event
FUNCTION:NAME
The DTrace probe name for the event
remaining fields
The first is the name of the process, the second is the file pathname.
DOCUMENTATION
See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver-
bose descriptions explaining the output.
EXIT
filebyproc.d will run forever until Ctrl-C is hit.
AUTHOR
Brendan Gregg [Sydney, Australia]
SEE ALSO
opensnoop(1M), dtrace(1M), truss(1)
version 1.00 May 15, 2005 filebyproc.d(1m)