Sponsored Content
Operating Systems AIX Determining how long device has been in defined state Post 302766467 by dukessd on Monday 4th of February 2013 07:01:49 PM
Old 02-04-2013
You could use alog to check the boot log file but on most systems I see they wrap at a couple of boots, or less, so it may be lost.

Just like the errlog file these are way too small by default.

The errlog is by default 1MB of disk space on a system with 4, 16, 64 GB ram, this is silly, turn it up people if you want to have any idea of what happened!

I've seen systems fill the errlog in less than a minute!
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hitting with custom port in CLOSE_WAIT state for long time in solaris 10

Hi, Occasionally I am getting the port state in CLOSE_WAIT for long time in the solaris server. I am not sure is it application problem or not. Because we are using port 9009 for Tomcat process in our web application, some time when I start the application, the port 9009 is in CLOSE_WAIT... (0 Replies)
Discussion started by: mgmk.84
0 Replies

2. AIX

Device Available / Define state

Hi, I would like to know wheather it is possible to make device in availabe state? if for same reason os is not able to make it in available state. and it is in define state. (2 Replies)
Discussion started by: manoj.solaris
2 Replies

3. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

4. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

5. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
binlog.conf(4)						     Kernel Interfaces Manual						    binlog.conf(4)

NAME
binlog.conf - binlogd configuration file SYNOPSIS
event_code.priority destination Where: Are the numeric codes specified in binlog.h and the binlogd(8) reference page. An aster- isk (*) specifies that all events should be selected. The code dumpfile Specifies the recovery of the kernel binary event log buffer from a crash dump. A severity level cannot be specified. Filters selected events as severe, high, and low. An asterisk (*) specifies that all events should be selected. A local file pathname to a log file, or a remote system hostname for remote logging of events. DESCRIPTION
The /etc/binlog.conf file is a system file that enables you to configure or filter events that are to be logged by the binary error logger, binlogd. The binlogd 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. If you want the binlogd daemon to use a configuration file other than the default, specify the file name with the following command: # bin- logd -f config_file Note that EVM subscribes to binlog events by default, and any configuration options you select will affect what events are available to EVM. You can filter and select binlog events using EVM utilities, as described in the EVM(5) reference page. EXAMPLES
The following is a sample /etc/binlog.conf file: # # binlogd configuration file # #format of a line: event_code.priority destination # # where: event_code - see codes in binlog.h and man page, # * = all events # priority - severe, high, low, * = all priorities # destination - local file pathname or remote system # hostname *.* /usr/adm/binary.errlog dumpfile /usr/adm/crash/binlogdumpfile crdlog /usr/adm/binary.crdlog 102.high /usr/adm/disk.errlog FILES
/etc/binlog.conf /etc/binlog.auth - Authorization file for remote logging. /usr/sys/include/dec/binlog/binlog.h - Common components of a binary event log record. RELATED INFORMATION
Commands: /usr/sbin/binlogd(8), EVM(5) System Administration delim off binlog.conf(4)
All times are GMT -4. The time now is 03:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy