10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,all.Well,I know someone has already asked this question before,however,It's too long before.So i post a new thread here.
Here is the issue.I have a shell script that use awk to calculate something and the script takes about 15 mins,it will use 100% CPU,and the system automatically killed the... (2 Replies)
Discussion started by: homeboy
2 Replies
2. UNIX for Dummies Questions & Answers
Hi reader,
I'm making a tool out of korn shell script that is running on a HP-UX server. But everytime i invoke the tool, it gets killed after a while (mid-process). I have tried re-running it a couple of times but each invocation ending up the same way ..
following is a snippet of the o/p... (8 Replies)
Discussion started by: clakkad
8 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I have a process which takes 13-15 mins for execution and its getting killed in the meantime.So can you please helpme out how to protect the process from getting killed.
Thanks in advance.
Regards,
Harika (9 Replies)
Discussion started by: harikagrp
9 Replies
4. UNIX for Dummies Questions & Answers
HI all,
I am very new to AIX (matter of fact Unix). We are currently automating out manual process using Unix Shell Scripting.
My wrote a shell script which will accept the name of the sas job as parameter, checks the existense of the sas file in the specified folder.
If it is not present,... (1 Reply)
Discussion started by: anubhav2020
1 Replies
5. Solaris
Hi all,
Currently I am using LDAP to store some network related data, When I run following script
./ns-slapd ldif2db
Execution of above script terminates displaying "Killed" on the console.
As far as I know, a process can be killed by two ways-
1. manually running " kill -9 <PID of LDAP... (1 Reply)
Discussion started by: akash_mahakode
1 Replies
6. Solaris
hi,
i am creating a daemon process for updating the file at regular interval.one problem with this is if anybody kills the daemon it wont update the file.anybody have idea how to rerun the daemon if it killed.the code is written in c++ in solaries environment.
thnaks & regards
suresh (8 Replies)
Discussion started by: suresh_rtp
8 Replies
7. Programming
We are forking a process B from process A and the process B should display the details it reads from process C(daemon process) continuously.
Let us say that the process C sents 100 packets.The process B receives all the 100 packets from the process C before it prints all details of 31... (1 Reply)
Discussion started by: cijkmysj
1 Replies
8. Programming
Hi,
I'm currently working on a project to help the analysis of malware from inside the kernel to avoid any kind of detection.
So I need to be able to read the process memory from my kernel module.
As of now, I'm stuck at converting a virtual memory address (for example 0x080483e8 found... (3 Replies)
Discussion started by: anonymoose
3 Replies
9. UNIX for Dummies Questions & Answers
Suppose we have the following process tree:
init-> ProcessA->processB->processC
then I kill processB
Who is the parent of the processC?
init or the processA (6 Replies)
Discussion started by: Puntino
6 Replies
10. UNIX for Dummies Questions & Answers
I have a process that is in the sleeping state "S" and I have tried to stop it with a run control script that I use to stop/start it - but it does not stop.
I have tried kill -9 <PID of process> with no change. I imagine that this process is sleeping with the kernel.
It does not respond to... (5 Replies)
Discussion started by: finster
5 Replies
syslog.conf(4) File Formats syslog.conf(4)
NAME
syslog.conf - configuration file for syslogd system log daemon
SYNOPSIS
/etc/syslog.conf
DESCRIPTION
The file /etc/syslog.conf contains information used by the system log daemon, syslogd(1M), to forward a system message to appropriate log
files and/or users. syslogd preprocesses this file through m4(1) to obtain the correct information for certain log files, defining LOGHOST
if the address of "loghost" is the same as one of the addresses of the host that is running syslogd.
A configuration entry is composed of two TAB-separated fields:
selector action
The selector field contains a semicolon-separated list of priority specifications of the form:
facility.level [ ; facility.level ]
where facility is a system facility, or comma-separated list of facilities, and level is an indication of the severity of the condition
being logged. Recognized values for facility include:
user Messages generated by user processes. This is the default priority for messages from programs or facilities not listed in
this file.
kern Messages generated by the kernel.
mail The mail system.
daemon System daemons, such as in.ftpd(1M)
auth The authorization system: login(1), su(1M), getty(1M), among others.
lpr The line printer spooling system: lpr(1B), lpc(1B), among others.
news Designated for the USENET network news system.
uucp Designated for the UUCP system; it does not currently use the syslog mechanism.
cron Designated for cron/at messages generated by systems that do logging through syslog. The current version of the Solaris
Operating Environment does not use this facility for logging.
audit Designated for audit messages generated by systems that audit by means of syslog.
local0-7 Designated for local use.
mark For timestamp messages produced internally by syslogd.
* An asterisk indicates all facilities except for the mark facility.
Recognized values for level are (in descending order of severity):
emerg For panic conditions that would normally be broadcast to all users.
alert For conditions that should be corrected immediately, such as a corrupted system database.
crit For warnings about critical conditions, such as hard device errors.
err For other errors.
warning For warning messages.
notice For conditions that are not error conditions, but may require special handling. A configuration entry with a level value of
notice must appear on a separate line.
info Informational messages.
debug For messages that are normally used only when debugging a program.
none Do not send messages from the indicated facility to the selected file. For example, a selector of
*.debug;mail.none
sends all messages except mail messages to the selected file.
For a given facility and level, syslogd matches all messages for that level and all higher levels. For example, an entry that specifies a
level of crit also logs messages at the alert and emerg levels.
The action field indicates where to forward the message. Values for this field can have one of four forms:
o A filename, beginning with a leading slash, which indicates that messages specified by the selector are to be written to the specified
file. The file is opened in append mode if it exists. If the file does not exist, logging silently fails for this action.
o The name of a remote host, prefixed with an @, as with: @server, which indicates that messages specified by the selector are to be
forwarded to the syslogd on the named host. The hostname "loghost" is treated, in the default syslog.conf, as the hostname given to
the machine that logs syslogd messages. Every machine is "loghost" by default, per the hosts database. It is also possible to specify
one machine on a network to be "loghost" by, literally, naming the machine "loghost". If the local machine is designated to be
"loghost", then syslogd messages are written to the appropriate files. Otherwise, they are sent to the machine "loghost" on the net-
work.
o A comma-separated list of usernames, which indicates that messages specified by the selector are to be written to the named users if
they are logged in.
o An asterisk, which indicates that messages specified by the selector are to be written to all logged-in users.
Blank lines are ignored. Lines for which the first nonwhite character is a '#' are treated as comments.
EXAMPLES
Example 1: A Sample Configuration File
With the following configuration file:
*.notice /var/log/notice
mail.info /var/log/notice
*.crit /var/log/critical
kern,mark.debug /dev/console
kern.err @server
*.emerg *
*.alert root,operator
*.alert;auth.warning /var/log/auth
syslogd(1M) logs all mail system messages except debug messages and all notice (or higher) messages into a file named /var/log/notice. It
logs all critical messages into /var/log/critical, and all kernel messages and 20-minute marks onto the system console.
Kernel messages of err (error) severity or higher are forwarded to the machine named server. Emergency messages are forwarded to all users.
The users root and operator are informed of any alert messages. All messages from the authorization system of warning level or higher are
logged in the file /var/log/auth.
FILES
/var/log/notice log of all mail system messages (except debug messages) and all messages of notice level or higher
/var/log/critical log of all critical messages
/var/log/auth log of all messages from the authorization system of warning level or higher
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Stable |
+-----------------------------+-----------------------------+
SEE ALSO
at(1), crontab(1), logger(1), login(1), lp(1), lpc(1B), lpr(1B), m4(1), cron(1M), getty(1M), in.ftpd(1M), su(1M), syslogd(1M), syslog(3C),
hosts(4), attributes(5)
SunOS 5.10 28 Jul 2004 syslog.conf(4)