Sponsored Content
Full Discussion: Display problem
Operating Systems Solaris Display problem Post 302107472 by RTM on Saturday 17th of February 2007 08:39:32 AM
Old 02-17-2007
What Solaris are you running (OS version, type/model of system, X86 or Sun)?

What, if any, errors are you seeing on the screen, in /var/adm/messages (or appropriate logging file)?
Is this happening for all users or just one? Have you tried logging in as root - do you get the same results?
Have you tried rebooting the box?
Can you login to the box remotely?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

X display problem...

I've checked all the documenttion that i can find here in the forums...and on the net....to no avail. Here's my scenario: I'm attempting to activate a remote X server. I 'm on a SuSe 7.0 distro, behind a firewall. (using bash shell) $ $ ifconfig eth0 192.168.1.203 up{as root} $ xhost +... (2 Replies)
Discussion started by: thomas.jones
2 Replies

2. Solaris

Display Problem

Hi, I am trying to install oracle client on unix(SUN Solaris) machine. For this a GUI window will open when i click ./runInstaller I have Humming Bird Connectivity ->Exceed .Now what i have to do ...?? Please tell me ASAP. Its urgent i need to install right away. This is a Solaris Machine. ... (1 Reply)
Discussion started by: dreams5617
1 Replies

3. Shell Programming and Scripting

Display Problem

Hi, I am trying to install oracle client on unix(SUN Solaris) machine. For this a GUI window will open when i click ./runInstaller I have Humming Bird Connectivity ->Exceed .Now what i have to do ...?? Please tell me ASAP. Its urgent i need to install right away. This is a Solaris Machine. ... (1 Reply)
Discussion started by: dreams5617
1 Replies

4. Shell Programming and Scripting

DATE display Problem

I have write echo `date +%y%m%d` but it will give 070529. why I am not getting 070530. I have Make any syntactical error? please help. (2 Replies)
Discussion started by: rinku
2 Replies

5. UNIX for Dummies Questions & Answers

xwd -display problem

Hi, Ive a problem with xwd. I want a snapshot from my second display. xwd -display :0.0 -root | xwdtopnm 2>/dev/null | pnmtopng > pic.png gives me a pic with both screens. I tested :0.1, :1.0; :1.1 but nothing works... what ive to choose for my second display (screen 1). Here my... (0 Replies)
Discussion started by: mcW
0 Replies

6. Solaris

Problem with display

Hi all, I have installed Solaris 10 on X-86. I installed successfully with all default installation parameters. After installation, when computer reboots, it doesn't come with display. Even screen sleeps without showing any error. Can anyone tell what could be the problem? Is the... (2 Replies)
Discussion started by: naw_deepak
2 Replies

7. UNIX for Dummies Questions & Answers

display problem

hi i have written a script #!/bin/sh clear menu() { ...... echo "enter 4 for finding text in a files" echo "input: \c" } switch() { read input case $input in ....... 4) echo "find" (1 Reply)
Discussion started by: the.noob
1 Replies

8. Solaris

display problem

i installed solaris 5.10 on my intel core 2 duo ....mercury board...evrything works fine ... but i get a black screen at desktop login...i cant see anything and im forced to reboot....every time get this prob on reboot .. i changed monitors....thinking there might be problem with monitor ... (2 Replies)
Discussion started by: vivek_ng
2 Replies

9. UNIX for Dummies Questions & Answers

DISPLAY Problem

We are facing an issue setting up Display on our server. Thu Jan 5 17:09:01 2012 vncext: VNC extension running! vncext: Listening for VNC connections on port 5905 vncext: created VNC server for screen 0 error opening security policy file /usr/lib/X11/xserver/SecurityPolicy... (1 Reply)
Discussion started by: narayanv
1 Replies

10. UNIX for Dummies Questions & Answers

Problem with VI display

Hi Experts, i am facing this problem with vi. Most of the time my vi display will show like below.it is hectic for me to .so again i have to do re size or maximize something like then it will come normal. HELP?? (2 Replies)
Discussion started by: prakumar
2 Replies
syslog.conf(4)							   File Formats 						    syslog.conf(4)

NAME
syslog.conf - configuration file for syslogd system log daemon SYNOPSIS
/etc/syslog.conf DESCRIPTION
The file /etc/syslog.conf contains information used by the system log daemon, syslogd(1M), to forward a system message to appropriate log files and/or users. syslogd preprocesses this file through m4(1) to obtain the correct information for certain log files, defining LOGHOST if the address of "loghost" is the same as one of the addresses of the host that is running syslogd. A configuration entry is composed of two TAB-separated fields: selector action The selector field contains a semicolon-separated list of priority specifications of the form: facility.level [ ; facility.level ] where facility is a system facility, or comma-separated list of facilities, and level is an indication of the severity of the condition being logged. Recognized values for facility include: user Messages generated by user processes. This is the default priority for messages from programs or facilities not listed in this file. kern Messages generated by the kernel. mail The mail system. daemon System daemons, such as in.ftpd(1M) auth The authorization system: login(1), su(1M), getty(1M), among others. lpr The line printer spooling system: lpr(1B), lpc(1B), among others. news Designated for the USENET network news system. uucp Designated for the UUCP system; it does not currently use the syslog mechanism. cron Designated for cron/at messages generated by systems that do logging through syslog. The current version of the Solaris Operat- ing Environment does not use this facility for logging. audit Designated for audit messages generated by systems that audit by means of syslog. local0-7 Designated for local use. mark For timestamp messages produced internally by syslogd. * An asterisk indicates all facilities except for the mark facility. Recognized values for level are (in descending order of severity): emerg For panic conditions that would normally be broadcast to all users. alert For conditions that should be corrected immediately, such as a corrupted system database. crit For warnings about critical conditions, such as hard device errors. err For other errors. warning For warning messages. notice For conditions that are not error conditions, but may require special handling. A configuration entry with a level value of notice must appear on a separate line. info Informational messages. debug For messages that are normally used only when debugging a program. none Do not send messages from the indicated facility to the selected file. For example, a selector of *.debug;mail.none sends all messages except mail messages to the selected file. For a given facility and level, syslogd matches all messages for that level and all higher levels. For example, an entry that specifies a level of crit also logs messages at the alert and emerg levels. The action field indicates where to forward the message. Values for this field can have one of four forms: o A filename, beginning with a leading slash, which indicates that messages specified by the selector are to be written to the specified file. The file is opened in append mode if it exists. If the file does not exist, logging silently fails for this action. o The name of a remote host, prefixed with an @, as with: @server, which indicates that messages specified by the selector are to be forwarded to the syslogd on the named host. The hostname "loghost" is treated, in the default syslog.conf, as the hostname given to the machine that logs syslogd messages. Every machine is "loghost" by default, per the hosts database. It is also pos- sible to specify one machine on a network to be "loghost" by, literally, naming the machine "loghost". If the local machine is designated to be "loghost", then syslogd messages are written to the appropriate files. Otherwise, they are sent to the machine "loghost" on the network. o A comma-separated list of usernames, which indicates that messages specified by the selector are to be written to the named users if they are logged in. o An asterisk, which indicates that messages specified by the selector are to be written to all logged-in users. Blank lines are ignored. Lines for which the first nonwhite character is a '#' are treated as comments. EXAMPLES
Example 1 A Sample Configuration File With the following configuration file: *.notice /var/log/notice mail.info /var/log/notice *.crit /var/log/critical kern,mark.debug /dev/console kern.err @server *.emerg * *.alert root,operator *.alert;auth.warning /var/log/auth syslogd(1M) logs all mail system messages except debug messages and all notice (or higher) messages into a file named /var/log/notice. It logs all critical messages into /var/log/critical, and all kernel messages and 20-minute marks onto the system console. Kernel messages of err (error) severity or higher are forwarded to the machine named server. Emergency messages are forwarded to all users. The users root and operator are informed of any alert messages. All messages from the authorization system of warning level or higher are logged in the file /var/log/auth. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
at(1), crontab(1), logger(1), login(1), lp(1), lpc(1B), lpr(1B), m4(1), cron(1M), getty(1M), in.ftpd(1M), su(1M), syslogd(1M), syslog(3C), hosts(4), attributes(5) SunOS 5.11 26 Apr 2006 syslog.conf(4)
All times are GMT -4. The time now is 07:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy