01-31-2001
Where is the messages log (like /var/adm/messages on Solaris) on an HP-UX box?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
Does anyone know if this is a patch error or a real memory problem, its happening a lot and wanted to know what to expect if I reboot it.
prtdiag shows no errors.
the system is anetra running solaris9 5.9 Generic sun4u sparc SUNW,UltraSPARC-IIi-cEngine
Jan 5 15:23:39 t1 last message... (1 Reply)
Discussion started by: sun-days
1 Replies
2. UNIX for Dummies Questions & Answers
I am receiving a repeating error in my /var/adm/messages, and I did a full Google search and search on this site. This site had 1 hit, but didn't really explain why it's occurring, Google didn't return much of value. Perhaps someone here has a potential fix:
Mar 20 07:17:52 <server_name>... (1 Reply)
Discussion started by: FredSmith
1 Replies
3. Shell Programming and Scripting
Hi All,
Since i am very new to shell scripting, i need help from you guys.
Suppose there is a file containing:
Log message:
Ashish
"asasasa"
asasa
asasa
asasas.info1
Log message:
Kapil
"asasasa"
asasa
asasa
asasas..info1 (2 Replies)
Discussion started by: ashish.kapil
2 Replies
4. HP-UX
Hello,
I am New to Unix.
I am Using HP-UX 9000 Series for my Application.
I am Currently Facing an Issue that the error messages are being written in the syslog file instead of the Application Log File. The Codes for that Syslog.h is written in Pro*C.
I want to know how to Redirect these... (3 Replies)
Discussion started by: balasubramaniam
3 Replies
5. Shell Programming and Scripting
Hi I have a file in which there are lot of redundancy messages..
Like suppose i have the messages like the following in my file..
45123|1|784tryr|uirirr|wagras|swyuyau||
45123|1|784tryr|uirirr|wagras|swyuyau||
I need to remove the extra (45123|1|784tryr|uirirr|wagras|swyuyau||) and need... (1 Reply)
Discussion started by: grajesh_955
1 Replies
6. Shell Programming and Scripting
I am looking for a script to do the following. I have a large log file that contains hundreds of warnings, a lot of which can be ignored. The tool doesn't allow me to suppress it, so I like to parse it out from the log file and isolate just the new messages/warnings, based on an exception file.
... (12 Replies)
Discussion started by: cdn2008
12 Replies
7. Solaris
Hi, The following messages are getting logged to messages file extensively while the omniback backup is going on
"NFS write error on host test.test.com: Read-only file system."
The system has nfs filesystems and we are backing it up at that time.
Any thoughts ?...
Appreciate it..... (8 Replies)
Discussion started by: amqstam
8 Replies
8. Shell Programming and Scripting
hello all.....
I have a shell script created by the user ABC.
in that script, am trying to push some echo messages into a Log file.....
eg: echo "error occurred" >
but for some reason, my echo messages are not getting redirected to my log file........:confused:
need ur urgent... (8 Replies)
Discussion started by: cmaroju
8 Replies
9. UNIX for Advanced & Expert Users
The following notice I am getting in /var/adm/messages file
Dec 9 06:17:24 hostname lw8: Main, up 476 days 04:42:23, Memory 9,742,808
Dec 9 10:17:25 hostname lw8: Main, up 476 days 08:42:23, Memory 10,179,864
But my actual uptime is ::
11:55am up 25 day(s), 10:38, 3 users, ... (5 Replies)
Discussion started by: brij123
5 Replies
10. UNIX for Dummies Questions & Answers
Hi folks,
In what circumstance does the log move to
/var/adm/messages.0.......messages.1,messages.2,messages.3 .......etc
---------- Post updated at 06:23 PM ---------- Previous update was at 06:17 PM ----------
To make my questions more understandable,
What are the processes that... (4 Replies)
Discussion started by: kimurayuki
4 Replies
LEARN ABOUT OSF1
syslog.conf
syslog.conf(4) Kernel Interfaces Manual syslog.conf(4)
NAME
syslog.conf - syslogd configuration file
SYNOPSIS
facility.severity destination Where: Is part of the system generating the message, specified in /usr/include/sys/syslog_pri.h.
See also the syslogd(8) reference page. The severity level, which can be emerg, alert, crit, err, warning, notice, info, or debug. See
/usr/include/sys/syslog_pri.h.
The syslogd daemon logs all messages of the specified severity level plus all messages of greater severity. For example, if you
specify level err, all messages of levels err, crit, alert, and emerg or panic are logged. A local file pathname to a log file, a
host name for remote logging or a list of users. In the latter case the users will receive messages when they are logged in. An
asterisk (*) causes a message to be sent to all users who are currently logged in.
DESCRIPTION
The /etc/syslog.conf file is a system file that enables you to configure or filter events that are to be logged by syslogd. You can specify
more than one facility and its severity level by separating them with semicolons.
You can specify more than one facility logs to the same file by separating the facilities with commas, as shown in the EXAMPLES section.
The syslogd daemon ignores blank lines and lines that begin with an octothorpe (#). You can specify # as the first character in a line to
include comments in the file or to disable an entry. The facility and severity level are separated from the destination by one or more tab
characters.
If you want the syslogd daemon to use a configuration file other than the default, you must specify the file name with the following com-
mand: # syslogd -f config_file
Daily Log Files
You can specify in the /etc/syslog.conf file that the syslogd daemon create daily log files. To create daily log files, use the following
syntax to specify the path name of the message destination: /var/adm/syslog.dated/ { file} The file variable specifies the name of the log
file, for example, mail.log or kern.log. If you specify a /var/adm/syslog.dated/file path name destination, each day the syslogd daemon
creates a sub-directory under the /var/adm/syslog.dated directory and a log file in the sub-directory, using the following syntax:
/var/adm/syslog.dated/ date / file Where: The date variable specifies the day, month, and time that the log file was created. The file
variable specifies the name of the log file you previously specified in the /etc/syslog.conf file. The syslogd daemon automatically cre-
ates a new date directory every 24 hours and also when you boot the system. The current directory is a link to the latest date directory.
To get the latest logs, you only need to reference the /var/adm/syslog.dated/current directory.
EXAMPLES
The following is a sample /etc/syslog.conf file: # # syslogd config file # # facilities: kern user mail daemon auth syslog lpr binary #
priorities: emerg alert crit err warning notice info debug # kern.debug /var/adm/syslog.dated/kern.log user.debug /var/adm/sys-
log.dated/user.log daemon.debug /var/adm/syslog.dated/daemon.log auth.crit;syslog.debug /var/adm/syslog.dated/syslog.log mail,lpr.debug
/var/adm/syslog.dated/misc.log msgbuf.err /var/adm/crash.dated/msgbuf.savecore kern.debug /var/adm/messages kern.debug /dev/console *.emerg
*
FILES
/etc/syslog.conf
/etc/syslog.auth - Authorization file for remote logging.
/usr/include/sys/syslog_pri.h - Common components of a syslog event log record.
RELATED INFORMATION
Commands: /usr/sbin/syslogd(8), /usr/sbin/binlogd(8)
System Administration delim off
syslog.conf(4)