Below is a test script to illustrate a problem from a larger script I am writing.
When I run this I receive the following output in /var/log/syslog.
Specifically I cannot understand where the "File descriptor 62 left open" and "File descriptor 63 left open" errors are coming from. Also the script hangs until I press enter.
I have done research but I am finding it difficult to understand whether these errors are related to lvm, syslog or something I am doing wrong in bash? let alone how to close the file descriptors properly.
---------- Post updated at 06:12 PM ---------- Previous update was at 12:01 PM ----------
I can now prevent the errors and know that the descriptors are from "logger" but I still do not understand it.
I added "62>&- 63>&-" to the end of each command and this resolves the errors e.g.
But what if the file descriptors where to change? How can I identify the relevant file descriptors and then close them? Do I need to even be concerned as they appear to close anyway?
Hi,
I have written a daemon process, to perform certain operations in the background.
For this I have to close, the open file descriptors,
Does anybody know how to find out the number of open file descriptors ?
Thanks in Advance,
Sheetal (2 Replies)
Hello all,
A few questions on file descriptors ...
scenario : Sun Ultra 30 with Sun OS 5.5.1 , E250 with Solaris 2.6
In one of my servers, the file descriptor status from the soft limit and hard limits are 64 and 1024 respectively for root user.
Is the soft limit (64) represents the... (3 Replies)
i m trying to learn processes in unix and i've been reading this but i don't quite get it. its regarding file descriptors. : each is a part of file pointers, they point to another area. indexes into an Operating system maintained table called "file descriptor table". one table per process. may... (3 Replies)
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)
Hi!
I currently run a very long script (two hour left...) on a remote computer through a ssh session. I wonder whats happend if I close the ssh session, or even, the terminal. Is the script running on remote will stop?
Thanks for your answers,
Tp (1 Reply)
Hello,
I have a Bash script that processes a text file so that the existing file will look something like this:
/www/repository/2010/201002231329532/LTLO_0407.pdf
/www/repository/2010/201002231329532/LTLO_0507.pdf
/www/repository/2010/201002231329532/LTLO_0607.pdf... (1 Reply)
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 :) (15 Replies)
I am running a process in nohup .
nohup getkeys.ksh 132 > 132.out &
When I close the putty terminal,The process is getting killed .
default_signal_handler called for signal no: 1
Is there a way to keep the process running even If I close the terminal (2 Replies)
Cygwin bash script was invoked in bash shell as follows:
/cygdrive/c/cygwin/bin/bash test.sh
This is content of my script
#!/bin/bash
#
exec 3</cygdrive/c/cygwin/home/work/part1.txt
read -u 3 x
echo $x
exec 3<&-
Commands work correctly when issued one at a time within bash shell.... (2 Replies)
Discussion started by: joed270
2 Replies
LEARN ABOUT NETBSD
logger
LOGGER(1) BSD General Commands Manual LOGGER(1)NAME
logger -- make entries in the system log
SYNOPSIS
logger [-is] [-d SD] [-f file] [-m msgid] [-p pri] [-t tag] [message ...]
DESCRIPTION
logger provides a shell command interface to the syslog(3) system log module.
Options:
-d sd Log this in the structured data (SD) field. (sd has to be passed as one argument and will require careful quoting when used from
the shell.)
-f file Log the specified file.
-i Log the process id of the logger process with each line.
-m msgid The MSGID used for the message.
-p pri Enter the message with the specified priority. The priority may be specified numerically or as a ``facility.level'' pair. For
example, ``-p local3.info'' logs the message(s) as informational level in the local3 facility. The default is ``user.notice''.
-s Log the message to standard error, as well as the system log.
-t tag Mark every line in the log with the specified tag.
message Write the message to log; if not specified, and the -f flag is not provided, standard input is logged.
EXIT STATUS
The logger utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
logger System rebooted
logger -p local0.notice -t HOSTIDM -f /dev/idmc
SEE ALSO syslog(3), syslogd(8)STANDARDS
The logger utility conforms to IEEE Std 1003.2-1992 (``POSIX.2'').
BSD May 14, 2010 BSD