06-17-2009
Did you look in root's home directory the content of the logs found in .dt etc..
Like errorlog, startlog etc...?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, I'm new to the whole X-windows environment.
Need help please..
Believe it or not- I have a licensed "Reflection".
I use the XDMCP host, and I can see 4 servers there.
2 of the servers are aix servers: one is ver 4.3, the other one is ver 5.
When I open a session to the aix4.3 a large... (2 Replies)
Discussion started by: sunbird
2 Replies
2. HP-UX
Hi All,
I m facing a problem that, i m not able to login as root user on cde on hp-ux 11.00, i can login as root on commond line as well as telnet. Thanks in Advance for help.
Regards,
Awadhesh (1 Reply)
Discussion started by: Awadhesh
1 Replies
3. HP-UX
Hi All,
I m facing a problem that, i m not able to login as root user on cde on hp-ux 11.00, i can login as root on commond line as well as telnet. Thanks in Advance for help.
Regards,
Awadhesh (2 Replies)
Discussion started by: Awadhesh
2 Replies
4. HP-UX
I've just completed a fresh install of HP-UX 11.0 on my 712/80 and everything starts up fine until it gets to the point where X kicks off and I believe at this point is supposed to launch into the CDE login.
It just sits there on the blank X screen with the X cursor for a minute or so then BEEPS... (9 Replies)
Discussion started by: ErikTheHAck
9 Replies
5. Solaris
Hi ,
I have SunBlade 150 Workstation (Solaris 9), I installed the OS again then when I try to login to any server using ( Options > Remote Login > Enter Host Name)
after I entered any host name nothing happened just white page for 2 or 3 mintues then the login screen reseted to the local... (4 Replies)
Discussion started by: adel8483
4 Replies
6. UNIX for Advanced & Expert Users
I'm having problem with the CDE pre login banner.
I configured the c/usr/dt/config/C/Xresources file to add my warning message:
Dtlogin*greeting.labelString: My Banner
I then modified the Dtlogin*greeting*fontList to display the message in smaller text. This did not work.
... (1 Reply)
Discussion started by: equismorio
1 Replies
7. Solaris
Dear All
I am in a strange situation where I have install the Solaris 10 5/08 OS on Netra 1280 server. When I connect it through my laptop so that I can take the GUI from xmanager. When I try to login as root or any other users also through Java Destop Environment which accepted it after few... (3 Replies)
Discussion started by: girish.batra
3 Replies
8. AIX
Hi, can somebody please, please help me?
After a power loss and server restart my server running AIX 4.2.2 could not boot. Following the procedure in my user guide
I checked the hd's with
# fsck -y /dev/hd1
# fsck -y /dev/hd2
# fsck -y /dev/hd3
# fsck -y /dev/hd4
# fsck -y /dev/hd9var
I... (0 Replies)
Discussion started by: semso
0 Replies
9. UNIX for Dummies Questions & Answers
Hi, can somebody please, please help me?
After a power loss and server restart my server running AIX 4.2.2 could not boot. Following the procedure in my user guide
I checked the hd's with
# fsck -y /dev/hd1
# fsck -y /dev/hd2
# fsck -y /dev/hd3
# fsck -y /dev/hd4
# fsck -y /dev/hd9var
... (4 Replies)
Discussion started by: semso
4 Replies
10. HP-UX
Hi all,
I canīt get a remote desktop login through CDE only with root user.
There are messages in the Xerror file:
/usr/bin/X11/xset: bad font path element (#0), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font... (5 Replies)
Discussion started by: the0m3n
5 Replies
LEARN ABOUT ULTRIX
elcsd.conf
elcsd.conf(5) File Formats Manual elcsd.conf(5)
Name
elcsd.conf - error logging configuration file
Description
The file contains information used by the daemon to configure error logging for the system. The system manager maintains this file. The
error logging daemon is dependent on the current order of the entries in the file. Do not change the order.
The information in the file shows any defaults and describes what you can enter. A newline is used to delimit each entry in the file, a
null entry consists of a newline alone, and comments begin with #.
#
# elcsd - errlog configuration file
#
{ # delimiter DON'T remove or comment out!
1 # status 1-local,2-logrem,4-remlog,5-remlog+priloglocal
# errlog file size limit num. of blocks
/usr/adm/syserr # errlog dir. path
# backup errlog dir. path
/ # single user errlog dir. path
/usr/adm/syserr # log remote hosts errlog dir. path
# remote hostname to log to
} # delimiter DON'T remove or comment out!
# hosts to log :S - separate file or :R - remotes file (together)
remote1:S
remote2:S
#remote3:S # disabled
remote4:S
.
.
.
The status line of the file describes where you can log error packets, also called error messages:
Logs error packets locally =
1, the default.
Logs error packets from a remote system or systems to the local machine =
2.
Logs local and remote error packets locally =
3.
Logs error packets from the local system to a remote system =
4.
Logs error packets from the local system remotely and logs high
priority messages locally = 5.
The errorlog file size defines the maximum size of an errorlog file. If disk space is limited, you can specify the maximum number of
blocks (512 bytes each) you want the errorlog file to be. If you do not specify the maximum number of blocks, the system will notify you
when the file system is 98% full.
The default errorlog directory path is You can direct error packets to a different directory; if you do, you must change the default for
also. For further information, see
If the error-logging daemon cannot write to the primary errorlog directory path, it attempts to log to the backup errorlog directory path
automatically.
The root directory is the default for the single-user errorlog directory path. When the system makes the transition to multiuser mode,
errors logged in single-user mode are transferred to the default errorlog directory path You can direct single-user error packets to
another directory.
To log error packets from a remote system locally, set up an errorlog directory path on the local system. The default is
Errorlog packets from remote systems can be logged to separate files or to one file. S sets up a separate errorlog file for each remote
system that logs locally. R logs packets from the corresponding remote system to the file syserr.remotes. The default is S.
Restrictions
You must have superuser privileges to change the file. However, anyone can view the file.
Files
elcsd daemon messages
See Also
elcsd(8), eli(8), uerf(8)
Guide to the Error Logger System
elcsd.conf(5)