9 More Discussions You Might Find Interesting
1. HP-UX
After install of the Sept. 2010 patch set on my hpux 11.23 system, my xterm when launched, dies immediately on the client with the xserver, with a core.xterm file in root of the hpux server. This had been working before the patch install.
I tried to find xterm patches from ITRC (yes the old... (1 Reply)
Discussion started by: mrmurdock
1 Replies
2. UNIX for Advanced & Expert Users
I am running eod8 to connect to a linux machine running
carnesr==>uname -a
Linux hostname 2.6.32-220.2.1.el6.x86_64 #1 SMP Tue Dec 13 16:21:34 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
I have a script that opens up several xterms as follows:
/usr/bin/xterm -geometry 150x60+0-0 -name... (1 Reply)
Discussion started by: rcarnesiii
1 Replies
3. Hardware
Hello,
I am having a problem with my wireless. Seems to be a relatively new problem over the past few weeks. I have an intel wireless. It seems like it can be fine for days, then in will quite working to the point a reboot is necessary. It may happen once and be fine, or may happen several times... (0 Replies)
Discussion started by: Narnie
0 Replies
4. IP Networking
We have a NAS application which can be accessed by both HTTP and HTTPS connections.
The issue we are facing is that the tcp server instance that initiates the HTTP access dies after a few hours of inactivity(the NAS application was kept idle for around 10 hours). However, the tcpserver that... (1 Reply)
Discussion started by: swatidas11
1 Replies
5. UNIX for Advanced & Expert Users
Hi,
I have over 5 gb of data in a files structure in which month folders are in year folders, day folders are in month folders, and individual climate stations are in each day. I am trying to extract precipitation measured at 5 minute intervals for a duration of 15 years, but the script never... (2 Replies)
Discussion started by: mlw63@me.com
2 Replies
6. Solaris
I noticed for some time now on solaris 8 whenever our root or oracle password expires after 12 weeks the cronjob for the expired user will totally stop working, it will start working again once the password has been changed.
I wonder if anybody encountered this problem and knows of a fix other... (4 Replies)
Discussion started by: sparcguy
4 Replies
7. Windows & DOS: Issues & Discussions
Hello All: I hope this is the right category...
I have a application (this app runs under java and jboss) that runs under Windows, it's started as a service. If that application should become disabled, crash or no longer function, what would be the best method for determining it is no longer... (6 Replies)
Discussion started by: jimmyc
6 Replies
8. Solaris
Say I have a daemon that dies for an unknown reason. Is there a way to track its process ID to try to determine when it dies and what causes it to go away? (2 Replies)
Discussion started by: Silver11
2 Replies
9. Shell Programming and Scripting
hi folks,
anybody there with suggestions on how to have an email sent to an address (if a certain job (jobA) ever dies. the concern is over the trigerring of sending the email (not the actual sending of the email)
1. is it possible for the job in question, jobA, itself do such a thing... (2 Replies)
Discussion started by: jacob_gs
2 Replies
syslog(8) System Manager's Manual syslog(8)
Name
syslog - log systems messages
Syntax
/etc/syslog [ -mN ] [ -fname ] [ -d ]
Description
The command reads a datagram socket and logs each line it reads into a set of files described by the configuration file The command config-
ures when it starts up and whenever it receives a hangup signal.
Each message is one line. A message can contain a priority code, marked by a digit in angle braces at the beginning of the line. Priori-
ties are defined in < syslog.h >, as follows:
LOG_ALERT This priority should essentially never be used. It applies only to messages that are so important that every user should be
aware of them, for example, a serious hardware failure.
LOG_SALERT Messages of this priority should be issued only when immediate attention is needed by a qualified system person, for example,
when some valuable system resource disappears. These messages are sent to a list of system people.
LOG_EMERG Emergency messages are not sent to users, but represent major conditions. An example might be hard disk failures. These
could be logged in a separate file so that critical conditions could be easily scanned.
LOG_ERR These messages represent error conditions, such as soft disk failures, etc.
LOG_CRIT Such messages contain critical information, but which can not be classed as errors, for example, `su' attempts. Messages of
this priority and higher are typically logged on the system console.
LOG_WARNING These messages are issued when an abnormal condition has been detected, but recovery can take place.
LOG_NOTICE These messages fall into the class of ``important information''; this class is informational but important enough that you
don't want to throw it away casually. Messages without any priority assigned to them are typically mapped into this priority.
LOG_INFO These are information level messages. These messages could be thrown away without problems, but should be included if you
want to keep a close watch on your system.
LOG_DEBUG These messages may be useful to log certain debugging information. Normally this information is thrown away.
It is expected that the kernel will not log anything below LOG_ERR priority.
The configuration file is in two sections separated by a blank line. The first section defines files that will log into. Each line con-
tains a single digit which defines the lowest priority (highest numbered priority) that this file will receive, an optional asterisk which
guarantees that something gets output at least every 20 minutes, and a pathname. The second part of the file contains a list of users that
will be informed on SALERT level messages. For example, the following logs all messages of priority 5 or higher onto the system console,
including timing marks every 20 minutes:
5*/dev/console
8/usr/spool/adm/syslog
3/usr/adm/critical
eric
kridle
kalash
This example logs all messages of priority 8 or higher into the file and all messages of priority 3 or higher into The users ``eric'',
``kridle'', and ``kalash'' will be informed on any subalert messages.
The flags are:
-m Set the mark interval to N (default 20 minutes).
-f Specify an alternate configuration file.
-d Turn on debugging (if compiled in).
To bring down, it should be sent a terminate signal. It logs that it is going down and then waits approximately 30 seconds for any addi-
tional messages to come in.
There are some special messages that cause control functions. ``<*>N'' sets the default message priority to N. ``<$>'' causes to recon-
figure (equivalent to a hangup signal). This can be used in a shell file run automatically early in the morning to truncate the log.
The command creates the file if possible containing a single line with its process ID. This can be used to kill or reconfigure
Restrictions
LOG_ALERT and LOG_SUBALERT messages should only be allowed to privileged programs.
Actually, can not deal with kernel error messages in the current implementation.
Files
Configuration file
Process id
See Also
syslog(3)
syslog(8)