09-23-2011
Closing open file descriptors from /proc/pid/fd
Hi guys,
i need to write a shell script that will close file descriptors from /proc/pid/fd
will calling
exec 4<&- solve the problem ?
thanks in advance
Last edited by rbatte1; 01-17-2017 at 07:54 AM..
Reason: ICode tags
10 More Discussions You Might Find Interesting
1. Cybersecurity
/* Linux Slackware */
Nmap shows the following ports open on the gateway.
21/tcp ftp
22/tcp ssh
23/tcp telnet
25/tcp smtp
37/tcp time
80/tcp http
113/tcp auth
515/tcp printer
587/tcp submission
1024/tcp kdm
6000/tcp x11
-------------------------------
i would like to close as... (10 Replies)
Discussion started by: LowOrderBit
10 Replies
2. 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
3. Cybersecurity
Hi!
I've a Java socket server program that is listening for requests, and using netstat, I can see that the connection is already open.
However as the process name (from ps -ef) is very long and I can't grep the program name. Can anyone advise how I find out the PID of the process? Can... (5 Replies)
Discussion started by: swing
5 Replies
4. Red Hat
hi,
i hav a query abt reading the contents of /proc/pid/maps file.is there any system apis or functions available to get the data from dat file and parse according to my need. i need name of the .so,Create date of the .so file.,Location of .so file etc.
please provide a good source.
yes i hav... (3 Replies)
Discussion started by: sanjaykhuntia
3 Replies
5. Shell Programming and Scripting
Below is a test script to illustrate a problem from a larger script I am writing.
$ cat /tmp/loggingtest
#!/bin/bash
lvcreate -s -l 100%FREE -n var-data-snapshot vg00/var-data 2> >(logger -t "loggingtest.crit") 1> >(logger -t "loggingtest.info")
sync &
wait
lvremove -f... (1 Reply)
Discussion started by: jelloir
1 Replies
6. Shell Programming and Scripting
i have a text file i.e file1.txt which shows open ports on particular system. i have another text file i.e file2.txt which shows a list of allowed ports on a system. for eg:
file2.txt
22/tcp ssh
23/tcp telnet.
can i have a script which would compare these text files ,file1 and file2 ... (1 Reply)
Discussion started by: anand121
1 Replies
7. Shell Programming and Scripting
Hi all,
I'm reading <advanced bash scripting> and there is a example to kill a background process in a limited time,as shown below:
#! /bin/bash
#set -n
TIMEOUT=$1
count=0
hanging_jobs & {
while ((count < TIMEOUT));do
eval ' && ((count = TIMEOUT))'
((count++))
sleep 1... (6 Replies)
Discussion started by: homeboy
6 Replies
8. UNIX for Dummies Questions & Answers
I think the libc.so is shared between processes, because it is a shared library and OS is engaged for saving memory.
But, below, the maps of bash, shows r-xp and r--p rw-p attributes to libc.so which mean private memory space.
Can anybody explain this for me?
:)cat /proc/$$/maps... (4 Replies)
Discussion started by: vistastar
4 Replies
9. Solaris
Hello all,
I have been tasked with finding the current open file descriptors versus the limit set. In Linux, this can be done like so:
cat /proc/sys/fs/file-nr
3391 969 52427
| | |
| | |
| | maximum open file descriptors
| total free allocated... (2 Replies)
Discussion started by: LinuxRacr
2 Replies
10. Shell Programming and Scripting
Hi all,
I have a small graphical application whose only purpose is to pop up certain types of messages. Currently, I'm using it in a Bash script like this:
./MyProg "this is my message"
while
do
... do things ...
done
What I want to do is after the while loop is over (it does... (4 Replies)
Discussion started by: Zel2008
4 Replies
EXEC(P) POSIX Programmer's Manual EXEC(P)
NAME
exec - execute commands and open, close, or copy file descriptors
SYNOPSIS
exec [command [argument ...]]
DESCRIPTION
The exec utility shall open, close, and/or copy file descriptors as specified by any redirections as part of the command.
If exec is specified without command or arguments, and any file descriptors with numbers greater than 2 are opened with associated redi-
rection statements, it is unspecified whether those file descriptors remain open when the shell invokes another utility. Scripts concerned
that child shells could misuse open file descriptors can always close them explicitly, as shown in one of the following examples.
If exec is specified with command, it shall replace the shell with command without creating a new process. If arguments are specified,
they shall be arguments to command. Redirection affects the current shell execution environment.
OPTIONS
None.
OPERANDS
See the DESCRIPTION.
STDIN
Not used.
INPUT FILES
None.
ENVIRONMENT VARIABLES
None.
ASYNCHRONOUS EVENTS
Default.
STDOUT
Not used.
STDERR
The standard error shall be used only for diagnostic messages.
OUTPUT FILES
None.
EXTENDED DESCRIPTION
None.
EXIT STATUS
If command is specified, exec shall not return to the shell; rather, the exit status of the process shall be the exit status of the program
implementing command, which overlaid the shell. If command is not found, the exit status shall be 127. If command is found, but it is not
an executable utility, the exit status shall be 126. If a redirection error occurs (see Consequences of Shell Errors ), the shell shall
exit with a value in the range 1-125. Otherwise, exec shall return a zero exit status.
CONSEQUENCES OF ERRORS
Default.
The following sections are informative.
APPLICATION USAGE
None.
EXAMPLES
Open readfile as file descriptor 3 for reading:
exec 3< readfile
Open writefile as file descriptor 4 for writing:
exec 4> writefile
Make file descriptor 5 a copy of file descriptor 0:
exec 5<&0
Close file descriptor 3:
exec 3<&-
Cat the file maggie by replacing the current shell with the cat utility:
exec cat maggie
RATIONALE
Most historical implementations were not conformant in that:
foo=bar exec cmd
did not pass foo to cmd.
FUTURE DIRECTIONS
None.
SEE ALSO
Special Built-In Utilities
COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol-
ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of
Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE
and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained
online at http://www.opengroup.org/unix/online.html .
IEEE
/The Open Group 2003 EXEC(P)