Have a look at "syslog.conf" file and check where it goes.
Traditiionally "stderr" defaults to the user output (screen) - it could have changed in Solaris 11.2 - but I'd be really surprised. You are looking for lines in the syslog.conf that will say something like.
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 a script that creates a KSH co-process for Oracle sqlplus and I am presently interacting with it via print -p and read -p.
I also need to interact with another Oracle database what isn't permitted to have any direct connection to the first. Presently, I simply disconnect from the first... (10 Replies)
I am in a Systems programming class this semester, and our current project is to write a program utilizing sockets and fork. For the project, I decided to make my own instant messaging program. I have the code completed, but I have a problem that keeps old clients from communicating with new... (3 Replies)
Dec 20 15:34:32 hostname sendmail: File descriptors missing on startup: stderr; Bad file number
Dec 20 15:34:32 hostname sendmail: File descriptors missing on startup: stderr; Bad file number
Dec 20 15:34:32 hostname sendmail: File descriptors missing on startup: stderr; Bad file number
Dec... (1 Reply)
Hi All,
This thread is going to be a discussion basically bringing out more information from the experts on cron jobs and the associated file handles.
So, here is the question.
There is definitely a constant ' n ' as the maximum number of file handles alloted to a process ' p '.
Will... (7 Replies)
I have written this code, and according to my research it SHOULD be going down the list until it is finished, but I am getting blank feedback. Nothing is being output as far as I can tell.
#!/bin/sh
while echo Enter to start traversing
read enter
do
read list <&3
echo $list
done
any... (2 Replies)
Hi,
I speak and write english more or less, so I hope my asking be clear.
:)
In the company I am working, they are using control-m software to lunch
shell scripts.
So i put this command in all shell scripts:
export LOGFILE_tmp=$PRODUC_DATA/tmp/${SCRIPT}_${PAIS}_`date... (0 Replies)
What is the difference between a file descriptor and a semaphore?
My basic understanding is:
- a file descriptor is a small positive integer that the system uses instead of the file name to identify an open file or socket.
- a semaphore is a variable with a value that indicates the... (1 Reply)
Discussion started by: Mr_Webster
1 Replies
LEARN ABOUT BSD
syslogd
SYSLOGD(8) System Manager's Manual SYSLOGD(8)NAME
syslogd - log systems messages
SYNOPSIS
syslogd [ -fconfigfile ] [ -mmarkinterval ] [ -d ]
DESCRIPTION
Syslogd reads and logs messages into a set of files described by the configuration file /etc/syslog.conf. Each message is one line. A
message can contain a priority code, marked by a number in angle braces at the beginning of the line. Priorities are defined in <sys/sys-
log.h>. Syslogd reads from the UNIX domain socket /dev/log, from an Internet domain socket specified in /etc/services, and from the spe-
cial device /dev/klog (to read kernel messages).
Syslogd configures when it starts up and whenever it receives a hangup signal. Lines in the configuration file have a selector to deter-
mine the message priorities to which the line applies and an action. The action field are separated from the selector by one or more tabs.
Selectors are semicolon separated lists of priority specifiers. Each priority has a facility describing the part of the system that gener-
ated the message, a dot, and a level indicating the severity of the message. Symbolic names may be used. An asterisk selects all facili-
ties. All messages of the specified level or higher (greater severity) are selected. More than one facility may be selected using commas
to separate them. For example:
*.emerg;mail,daemon.crit
Selects all facilities at the emerg level and the mail and daemon facilities at the crit level.
Known facilities and levels recognized by syslogd are those listed in syslog(3) without the leading ``LOG_''. The additional facility
``mark'' has a message at priority LOG_INFO sent to it every 20 minutes (this may be changed with the -m flag). The ``mark'' facility is
not enabled by a facility field containing an asterisk. The level ``none'' may be used to disable a particular facility. For example,
*.debug;mail.none
Sends all messages except mail messages to the selected file.
The second part of each line describes where the message is to be logged if this line is selected. There are four forms:
o A filename (beginning with a leading slash). The file will be opened in append mode.
o A hostname preceeded by an at sign (``@''). Selected messages are forwarded to the syslogd on the named host.
o A comma separated list of users. Selected messages are written to those users if they are logged in.
o An asterisk. Selected messages are written to all logged-in users.
Blank lines and lines beginning with `#' are ignored.
For example, the configuration file:
kern,mark.debug /dev/console
*.notice;mail.info /usr/spool/adm/syslog
*.crit /usr/adm/critical
kern.err @ucbarpa
*.emerg *
*.alert eric,kridle
*.alert;auth.warning ralph
logs all kernel messages and 20 minute marks onto the system console, all notice (or higher) level messages and all mail system messages
except debug messages into the file /usr/spool/adm/syslog, and all critical messages into /usr/adm/critical; kernel messages of error
severity or higher are forwarded to ucbarpa. All users will be informed of any emergency messages, the users ``eric'' and ``kridle'' will
be informed of any alert messages, and the user ``ralph'' will be informed of any alert message, or any warning message (or higher) from
the authorization system.
The flags are:
-f Specify an alternate configuration file.
-m Select the number of minutes between mark messages.
-d Turn on debugging.
Syslogd creates the file /var/run/syslog.pid, if possible, containing a single line with its process id. This can be used to kill or
reconfigure syslogd.
To bring syslogd down, it should be sent a terminate signal (e.g. kill `cat /var/run/syslog.pid`).
FILES
/etc/syslog.conf the configuration file
/var/run/syslog.pid the process id
/dev/log Name of the UNIX domain datagram log socket
/dev/klog The kernel log device
SEE ALSO logger(1), syslog(3)4.2 Berkeley Distribution November 16, 1996 SYSLOGD(8)