08-07-2008
Quote:
Originally Posted by
dsbeerf
If you haven't specifically changed your DISPLAY variable (manually, or in a '.profile'), it is most likely set to: ':0'
Also, if you have done a 'su' to root in your "terminal", most likely you will NOT have permission to access the X server.
So, first do: "DISPLAY=:0;export DISPLAY" [or "setenv DISPLAY ':0'" for csh/tcsh.]
Then try the admintool again. If it does not work, then:
If you DID 'su' to root, open another command window (xterm, dtterm, etc.) as YOU (not root), and do: "xhost +"
This will allow you, as root, to 'connect' to the X server with your command 'admintool'.
B.T.W.: admintool will be eliminated in Solaris 10.
==
My set up is this:
I have a Sunfire V100 server running Solaris 8. ip address 192.168.1.250.
I cave a windows XP laptop and xwin32 installed. ip address 192.168.1.64
I can used xwin32 to bring up a CDE. Then a terminal window. From there I can su to root. (su -) But admin tool would not work. Error: Cannot open Display.
I used the above steps to resolve this issue, but first I needed to know the display.
- Log into CDE with regular user
- Bring up terminal window (whilst logged in as regular user)
- At the prompt type: echo $DISPLAY
-> It returned a line: 192.168.1.64:1.0
- Switch user to root: su -
-> enter root password
- At the # prompt type: DISPLAY=192.168.1.64:1.0 ; export DISPLAY
admintool &
and voila!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
Does anyone here know where I can find out what commands admintool runs while adding a new user and setting up the account? Reason being is the script I am writting, I can add the user create the path. But it wont set the path for the user. The password well it wont add without... (1 Reply)
Discussion started by: merlin
1 Replies
2. UNIX for Dummies Questions & Answers
hi, i tried these sun command on a sun0s 5.7 but get the "cant open display" message. please advise. i am using netterm to telnet. (5 Replies)
Discussion started by: yls177
5 Replies
3. UNIX for Dummies Questions & Answers
hi, after i execute admintool, i got the below
"Error, cant open display"
what is wrong?
thanks (5 Replies)
Discussion started by: yls177
5 Replies
4. UNIX for Dummies Questions & Answers
hi, i did the following
1) which admintool
/bin/admintool
2) admintool
Error: Can't open display:
how to set the display then? i am using netterm to telnet to my sun server. (6 Replies)
Discussion started by: yls177
6 Replies
5. UNIX for Dummies Questions & Answers
I am new to unix....How do I enable XWindows... Or for that matter, use Admintool. .....Pls. help.
Thanks.
PS. I am running Solaris 8. (3 Replies)
Discussion started by: d4jtwvb
3 Replies
6. UNIX for Advanced & Expert Users
Hi
I have a unix box [ Solaris 2.5.1 , sparc staion 5_10 )
I could successfully configure a LOCAL printer using
lpadmin -p XX -v /dev/term/a
But when I tried to do local printer configuration with admintool, ( as root user ) it throws up error. " add printer failed ".
Also when I... (4 Replies)
Discussion started by: shibz
4 Replies
7. Solaris
Hi all,
I'm trying to launch admintool via an export DISPLAY.
i get the message: Received communication service error 4: Remote procedure call timed out: program = 100087, version = 10
Just to say, i don't use nis/nisplus on my server...
What to do?
Thanx
Jason (17 Replies)
Discussion started by: penguin-friend
17 Replies
8. Solaris
what happened to admintool in Solaris10? (2 Replies)
Discussion started by: mndavies
2 Replies
9. UNIX for Advanced & Expert Users
Hi: I was setting up a modem on an Ultra5 running 2.6. (yes I know, how quaint)
There are 15 systems that are interlinked but not accessible to the outside world.
This will end soon with new updated sun systems but until then the system needs to be accessed by the outside world. Hence the... (1 Reply)
Discussion started by: mndavies
1 Replies
10. Solaris
Jetadmin fails saying that it is not a network printer despite the fact that it is and can be pinged from UNIX.
I am administering this remotely (long remote, I can't go there soon) and can't run smc or admintool.
Any help configuring this spooler would be appreciated. (1 Reply)
Discussion started by: TT Fan
1 Replies
XON(1) General Commands Manual XON(1)
NAME
xon - start an X program on a remote machine
SYNOPSIS
xon remote-host [-access] [-debug] [-name window-name] [-nols] [-screen screen-no] [-user user-name] [command ...]
DESCRIPTION
Xon runs the specified command (default xterm -ls) on the remote machine using rsh, remsh, or rcmd. Xon passes the DISPLAY, XAUTHORITY and
XUSERFILESEARCHPATH environment variables to the remote command.
When no command is specified, xon runs 'xterm -ls'. It additionally specifies the application name to be 'xterm-remote-host' and the win-
dow title to be '-fIremote-host'.
Xon can only work when the remote host will allow you to log in without a password, by having an entry in the .rhosts file permitting
access.
OPTIONS
Note that the options follow the remote host name (as they do with rlogin).
-access
Runs xhost locally to add the remote host to the host access list in the X server. This won't work unless xhost is given permission
to modify the access list.
-debug Normally, xon disconnects the remote process from stdin, stdout and stderr to eliminate the daemon processes which usually connect
them across the network. Specifying the -debug option leaves them connected so that error messages from the remote execution are
sent back to the originating host.
-name window-name
This specifies a different application name and window title for the default command (xterm).
-nols Normally xon passes the -ls option to the remote xterm; this option suspends that behaviour.
-screen screen-no
This changes the screen number of the DISPLAY variable passed to the remote command.
-user user-name
By default, xon simply uses rsh/remsh/rcmd to connect to the remote machine using the same user name as on the local machine. This
option cause xon to specify an alternative user name. This will not work unless you have authorization to access the remote
account, by placing an appropriate entry in the remote users .rhosts file.
BUGS
Xon can get easily confused when the remote-host, user-name or various environment variable values contain white space.
Xon has no way to send the appropriate X authorization information to the remote host.
X Version 11 scripts 1.0.1 XON(1)