Sponsored Content
Full Discussion: System boot up log file
Operating Systems Solaris System boot up log file Post 302080894 by efang on Thursday 20th of July 2006 10:03:40 PM
Old 07-20-2006
System boot up log file

Hi,

where can I check the system boot up log file like those message when the system booting up....

Thanks.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

System boot configuration

On my PC I have two hard disks, the first with Windows 98 SE and the second with Linux Mandrake 8.0 (Traktopel). When I have installed Linux, it has modified the boot record of the 1st HD and it has added a graphic menu (LILO) for selecting the OS to use. By default, if I don't press a key, Linux... (2 Replies)
Discussion started by: robotronic
2 Replies

2. UNIX for Advanced & Expert Users

Cannot boot - Boot : Panic : File size out of range (EWS-UX/V unix)

Hey ! I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range. According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies

3. UNIX for Dummies Questions & Answers

Boot from a remote system

I have a diskless work station. i want to boot from a remote linux machine. what changes i will have to do in configuration. Plz tell me thanks (1 Reply)
Discussion started by: hemant29
1 Replies

4. SCO

Can't boot system--help

I get a message saying Not enough space to dump xxxxx pages Press any key to reboot Safe to power off After rebooting it never gets to the "Press CTRL D to continue or enter password for single user" message before it goes back to "Not enough space..." message above. Vicious cycle. ... (0 Replies)
Discussion started by: deloev
0 Replies

5. UNIX for Dummies Questions & Answers

help boot system erro

being nosey on sons laptop and set a password and now need to undo this but its in the boot system :eek::eek::eek: (4 Replies)
Discussion started by: hempel
4 Replies

6. Solaris

System will not boot

We have a system that won't boot. It is Sun V245 that was patched yesterday with the latest Recommended 10 patch cluster. I will post what we get during the boot at the end of the email message. We have tried rebuilding the bootblk, booting from the cdrom, and running an fsck, booting into failsafe... (2 Replies)
Discussion started by: brownwrap
2 Replies

7. Solaris

dual boot solaris/solaris zfs file system

Hi, I am running into a some problems creating a dual boot system of 2 solaris instances using ZFS file system and I was wondering if someone can help me out. First some back ground. I have been asked to change the file system of our server from UFS to ZFS. Currently we are using Solaris... (3 Replies)
Discussion started by: estammis
3 Replies

8. HP-UX

File system full, won't complete boot

Hello, I have a very old hp rp2450 running 11i2 that I had to power off. When turning it back on it hangs with the following message. Would booting into SUM get me any further? I've never used SUM, so I'm asking before I go down that rabbit hole. Thanks for the help. # ## extra content... (1 Reply)
Discussion started by: calabaria
1 Replies

9. Red Hat

System fail to boot

Hi im using centos 6.4 starting yesterday i have a strange issue that im unable to resolve. the system is booting to GRUB menu and the os is not starting. i tried to run a repair install and the message attached is what i get, what can cause this? thanks, (1 Reply)
Discussion started by: guy3145
1 Replies

10. UNIX for Advanced & Expert Users

System cannot boot up

Hi, I got stuck in a very messy situation yesterday after attempting to resolve a filesystem full issue. The user reported that their filesystem (/var/DWS) was 100% full even after moving few files of sizes 14G, 30G and 50G out of the directory. I checked the filesystem once more after this... (5 Replies)
Discussion started by: anaigini45
5 Replies
strerr(8)						      System Manager's Manual							 strerr(8)

NAME
strerr - Receives error messages from the STREAMS log driver SYNOPSIS
/usr/sbin/strerr [-a sys_admin_mail_name] [-d logdir] PARAMETERS
Specifies the mail name of the user to receive the message via mail. This is the system administrator by default. Specifies the directory to contain the error log file. This is /var/adm/streams by default. DESCRIPTION
The strerr daemon receives error messages from the STREAMS log driver (strlog) for addition to the STREAMS error log files (error.mm.dd) in the STREAMS error logger directory (/var/adm/streams by default). When first called, the strerr daemon creates the log file error.mm.dd. This is a daily log file, where mm indicates the month and dd indicates the day of the logged messages. The strerr daemon then appends each error message that it subsequently receives from the STREAMS log driver to the log file. STREAMS error log messages have the following format: seq_num std_time ticks_time flags mod_ID sub_ID msg_text where: The error sequence number. The time the message was sent, in the format hh:mm:ss. The time the message was sent, measured in machine ticks since the last boot. Can be any of the following indicators: Indicates that the message has also been saved in the process's trace log. Indi- cates that the message signaled a fatal error. Indicates that the message is to be sent to the system administrator or specified user via mail. The module identification number of the trace message source. The subidentification number of the trace message source. The trace message text. The strerr daemon will run continuously until terminated by the user. FILES
The error log file or files on which strerr operates. NOTES
Only one strerr process can open the STREAMS log driver at a time. This restriction is intended to maximize performance. The STREAMS error logging mechanism works best when it is not overused. The strerr daemon can degrade STREAMS performance by affecting the response, throughput, and other behaviors of the drivers and modules that invoke it. The daemon will also fail to capture messages if drivers and modules generate messages at a higher rate than its optimum read rate. Missing sequence numbers among the messages in a log file indicate that messages have been lost. RELATED INFORMATION
Interfaces: strlog(7). delim off strerr(8)
All times are GMT -4. The time now is 05:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy