Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Can't Open Display localhost:0.0 Post 302509881 by garethnsolomons on Friday 1st of April 2011 01:51:26 AM
Old 04-01-2011
That was one of the first things I checked and it is off.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to open display from windows to solaris?

How can I telnet from my windows XP machine to my Ultra 60 and run firefox? I am unable to open the display using /usr/openwin/bin/xhost like I do from one Sun machine to another? Thanks (2 Replies)
Discussion started by: ridgeback00
2 Replies

2. UNIX for Dummies Questions & Answers

xhost: unable to open display????

I am a dba, not an sa, that recently had to take over administering an HP-UX server. Needless to say I am not in a comfortable area, but found out that of all people I am the most knowledgeable on unix here .... scary thought I know. I am having troubles exporting my display to a Windows XP... (5 Replies)
Discussion started by: soestx
5 Replies

3. UNIX for Advanced & Expert Users

xhost unable to open display

I am trying to install ORACLE 10g database on HP-UNIX 11.11 I am running OUI runinstaller from exceed terminal from windows PC. I have set DISPLAY=IPAddress of PC:0.0 When installer starts it is giving me error of display (5 Replies)
Discussion started by: ymg
5 Replies

4. UNIX for Advanced & Expert Users

localhost problem!

hello guys, this morning when I start my pc (gentoo) I get some strange errors about localhost. "Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName" ... Apache the same for my aplications, I have to use the full address of my pc instead of... (1 Reply)
Discussion started by: georgeplus
1 Replies

5. UNIX for Dummies Questions & Answers

"Gtk-WARNING cannot open display" from ssh

I am trying to do something on another computer through ssh and I keep getting this:"(gedit:6169): Gtk-WARNING **: cannot open display:"I have googled the interweb and this forum and found many posts but nothing seems to work. I have freshly installed Ubuntu 8.10 with updates on the machine and I... (4 Replies)
Discussion started by: badrabbit6
4 Replies

6. Red Hat

Error: Can't open display: :0.0

Hi, I get errors while running xclock from a non root user: # xclock --- this works fine # su - girish $ DISPLAY=:0.0; export DISPLAY $ xclock Xlib: connection to ":0.0" refused by server Xlib: No protocol specified Error: Can't open display: :0.0 $ I basically want to... (4 Replies)
Discussion started by: girish1428
4 Replies

7. Solaris

X11 and "Cannot Open Display" errors

Greetings Forumers! I'm posting a solution to an Issue I ran into this week: Getting applications to display on another through X11 and SSH. I have run into this issue many years ago and finally found my notes. Some of you may already know the answer to this issue but it took me a while to... (1 Reply)
Discussion started by: bluescreen
1 Replies

8. UNIX for Dummies Questions & Answers

xWindows error: xhost unable to open display

I am trying to direct a AIX display to my XWindows and I am at a dead end now! So this what I've done so far: 1. In putty settings, I set "Enable X11 forwarding" and also set "X diplay location" to "localhost:0" (without quotes, of course) 2. Via putty, connected to my AIX server 3. On... (1 Reply)
Discussion started by: shoefiend
1 Replies

9. Linux

(PMT:6498): Gtk-WARNING **: cannot open display:

Hai (PMT:6498): Gtk-WARNING **: cannot open display: how to solve this in linux Double post.. continue here (0 Replies)
Discussion started by: vinayd
0 Replies

10. Red Hat

(PMT:6498): Gtk-WARNING **: cannot open display:

Error message: (PMT:6498): Gtk-WARNING **: cannot open display: How to solve this issue in linux? (1 Reply)
Discussion started by: vinayd
1 Replies
INNCHECK(8)						      System Manager's Manual						       INNCHECK(8)

NAME
inncheck - check inn configuration and database files. SYNOPSIS
inncheck [ -a ] [ -v ] [ -pedantic ] [ -f ] [ -perm ] [ -noperm ] [ file=value | file ] DESCRIPTION
Inncheck examines various configuration files and databases and verifies things about them. Things verified depend on the file being checked, but generally are things like permissions, ownership, syntax errors in config files etc. Inncheck does not make changes to any files -- it just reports what it thinks may be wrong, and it is up to the operator to fix the prob- lem. The set of files checked may be restricted by using file or file=value arguments. For example, putting hosts.nntp causes only the hosts.nntp(5) file to be checked. Using hosts.nntp=/tmp/hosts.nntp.tst on the command line will cause inncheck to only verify the hosts.nntp file, and it will perform the checks on the file /tmp/hosts.nntp file instead of the default one. Valid values for file are: active control.ctl expire.ctl hosts.nntp inn.conf moderators newsfeeds overview.fmt nnrp.access nntpsend.ctl passwd.nntp OPTIONS
-a If any ``file'' value or ``file=value'' pairs (see below) are given, then normally only the files they refer to are checked. Use the ``-a'' flag to specify that all files should be checked regardless. In this case the form file=value will be the more useful. -v Use the ``-v'' option to get more verbose output. -pedantic Use the ``-pedantic option to get reports on things that are not necessarily wrong, but may indicate a bad configuration -- such as inn.conf(5) missing a key. -f Use the ``-f'' flag to have inncheck print the appropriate chown/chgrp/chmod command necessary to fix a problem that it reports. Any other output lines will be prefixed with a ``#'' character to make the output be valid input for a shell. Note that the ``-perm'' flag must be used as well when using this flag. -perm Inncheck checks all files for permission problems. If the ``-perm'' flag is used, then only the files specified by the file or file=value command line arguments will be checked for problems other than permission problems. -noperm To avoid doing any checking of file permissions or ownership, use the ``-noperm'' option. EXAMPLES
To have inncheck check all files for syntax and permission problems simply: inncheck To have inncheck check all files for permission problems and to verify the syntax of the active and hosts.nntp files do: inncheck -perm active hosts.nntp To have inncheck check the test newsfeeds file in /var/tmp/newsfeeds.testing, do: inncheck newsfeeds=/var/tmp/newsfeeds.testing To have inncheck check all the files as it normally does, but to specify a different location for the newsfeeds file, so: inncheck -a newsfeeds=/var/tmp/newsfeeds.testing BUGS
If the ``-f'' and ``-perm'' options are used together, along with -a or some ``file'' or ``file=value'' arguments that refer to a file with a syntax problem, then the output will no longer be valid input for a shell. HISTORY
Written by Brendan Kehoe <brendan@cygnus.com> and Rich Salz <rsalz@uunet.uu.net> This is revision 1.1, dated 1996/10/29. SEE ALSO
active(5), expire.ctl(5), history(5), hosts.nntp(5), inn.conf(5), newsfeeds(5) INNCHECK(8)
All times are GMT -4. The time now is 06:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy