Sponsored Content
Full Discussion: Xterm problem on Solaris 10
Operating Systems Solaris Xterm problem on Solaris 10 Post 302080008 by fusejj on Friday 14th of July 2006 02:18:37 PM
Old 07-14-2006
Xterm problem on Solaris 10

I apologize but didn't find an answer in the Discussions. I use an Exceed xterm just fine with Solaris 8 but it fails to connect to Solaris 10 server:

Xterm command line: DISPLAY=@d;export DISPLAY;/usr/openwin/bin/xterm

Failure message: "Unable to connect to host using specified start method"

I tried changing XServer type to "SUN" form "Xorg" using kdmconfig, but it didn't matter.

I can't enter the command: "export DISPLAY" at the command line, and am thinking that's the problem. Is this a Solaris 10 difference?

Thank you.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Xterm

Guys: Anyone have ideas on where can I get information or references if I want to learn on how to program with UNIX GUIs? If you do have ideas please let me know. Its a big help. (2 Replies)
Discussion started by: jfsuminist
2 Replies

2. UNIX for Dummies Questions & Answers

xterm

Would someone tell me how to save changes in xterm once I've made them using the program options? For example, I type: xterm -bg red and my console window changes color. But how can I now make this attribute save, so that it becomes the default when I relaunch xterm? Any help you can offer... (1 Reply)
Discussion started by: af6
1 Replies

3. UNIX for Dummies Questions & Answers

xterm?

Hello all, This is a lame question because I have been working with unix for some years now, but anyway here it is; What is an xterm? ivo (1 Reply)
Discussion started by: Ivo
1 Replies

4. Shell Programming and Scripting

xterm help?

I want to add a title to this xterm window but cannot figure out how. Can anybody assist with this? xterm +sb -geom 80x25 -ls -tn xterms -tm "intr ^q" -name unikix -e $UNIKIX/bin/unikixl (1 Reply)
Discussion started by: douknownam
1 Replies

5. UNIX for Dummies Questions & Answers

xterm

hi I'm trying to launch admintool via an export DISPLAY. that is i am doing a rlogin to serverB from serverA. i did the command export DISPLAY=serverA:0 but it prompted me the error DISPLAY=serverA:0: is not an identifier i have searched the forum but there is not much things on this error... (3 Replies)
Discussion started by: legato
3 Replies

6. UNIX for Dummies Questions & Answers

Problem with xterm & tcsh & sourcing a script in a single command

Hi friends, I have a script that sets the env variable path based on different conditions. Now the new path variable setting should not done in the same terminal or same shell. Only a new terminal or new shell should have the new path env variable set. I am able to do this only as follows: >cd... (1 Reply)
Discussion started by: sowmya005
1 Replies

7. UNIX for Dummies Questions & Answers

Problem with xterm scrollbar

I have a xterm window opening from my Java code. This xterm is opened from the code in this manner: // to run shell command in a xterm window public synchronized void rshd(String title, String commd) { String xt = "xterm -sb -T "; String xtm = xt + title + " -e " + commd; Runtime run =... (1 Reply)
Discussion started by: vanz
1 Replies

8. Solaris

Solaris 8 -> Solaris 10 = problem :/

Hello, I have a multithreading program (just two threads) which works on Solaris 8. I use pthread library to synchronize threads. I try to run it on Solaris 10 (on another computer). All sources was re-compiled but behaviour of my program is not the same. The thread 2 is never executed when... (3 Replies)
Discussion started by: Tinkh
3 Replies

9. Slackware

xterm problem?

My understanding is that /usr/share/terminfo/x/ is populated from a standard set of files and not by compiling, i.e. tic, termcaps. I am getting from both regular user and root when issuing: man tic ------> WARNING: terminal is not fully functional tset -q --------> xterm: unknown terminal type... (2 Replies)
Discussion started by: slak0
2 Replies

10. UNIX for Dummies Questions & Answers

Solaris +vi (not vim) not using xterm termcap entry

Well, apparently anyway. I have a Solaris 10/08 install using vi (not vim) and when I use vi to edit a file or go into cron, the screen goes into 25/80 mode and I have to send a reset or hard reset to get it back to my screen size (190x72 in this case). vi should be using the TERM environment... (7 Replies)
Discussion started by: BOFH
7 Replies
XINIT(1)                                                      General Commands Manual                                                     XINIT(1)

NAME
xinit - X Window System initializer SYNOPSIS
xinit [ [ client ] options ... ] [ -- [ server ] [ display ] options ... ] DESCRIPTION
The xinit program is used to start the X Window System server and a first client program on systems that are not using a display manager such as xdm(1) or in environments that use multiple window systems. When this first client exits, xinit will kill the X server and then terminate. If no specific client program is given on the command line, xinit will look for a file in the user's home directory called .xinitrc to run as a shell script to start up client programs. If no such file exists, xinit will use the following as a default: xterm -geometry +1+1 -n login -display :0 If no specific server program is given on the command line, xinit will look for a file in the user's home directory called .xserverrc to run as a shell script to start up the server. If no such file exists, xinit will use the following as a default: X :0 Note that this assumes that there is a program named X in the current search path. The site administrator should, therefore, make a link to the appropriate type of server on the machine, or create a shell script that runs xinit with the appropriate server. Note, when using a .xserverrc script be sure to ``exec'' the real X server. Failing to do this can make the X server slow to start and exit. For example: exec Xdisplaytype An important point is that programs which are run by .xinitrc should be run in the background if they do not exit right away, so that they don't prevent other programs from starting up. However, the last long-lived program started (usually a window manager or terminal emula- tor) should be left in the foreground so that the script won't exit (which indicates that the user is done and that xinit should exit). An alternate client and/or server may be specified on the command line. The desired client program and its arguments should be given as the first command line arguments to xinit. To specify a particular server command line, append a double dash (--) to the xinit command line (after any client and arguments) followed by the desired server command. Both the client program name and the server program name must begin with a slash (/) or a period (.). Otherwise, they are treated as an arguments to be appended to their respective startup lines. This makes it possible to add arguments (for example, foreground and back- ground colors) without having to retype the whole command line. If an explicit server name is not given and the first argument following the double dash (--) is a colon followed by a digit, xinit will use that number as the display number instead of zero. All remaining arguments are appended to the server command line. EXAMPLES
Below are several examples of how command line arguments in xinit are used. xinit This will start up a server named X and run the user's .xinitrc, if it exists, or else start an xterm. xinit -- /usr/local/bin/Xvnc :1 This is how one could start a specific type of server on an alternate display. xinit -geometry =80x65+10+10 -fn 8x13 -j -fg white -bg navy This will start up a server named X, and will append the given arguments to the default xterm command. It will ignore .xinitrc. xinit -e widgets -- ./Xorg -l -c This will use the command .Xorg -l -c to start the server and will append the arguments -e widgets to the default xterm command. xinit /usr/ucb/rsh fasthost cpupig -display ws:1 -- :1 -a 2 -t 5 This will start a server named X on display 1 with the arguments -a 2 -t 5. It will then start a remote shell on the machine fasthost in which it will run the command cpupig, telling it to display back on the local workstation. Below is a sample .xinitrc that starts a clock, several terminals, and leaves the window manager running as the ``last'' application. Assuming that the window manager has been configured properly, the user then chooses the ``Exit'' menu item to shut down X. xrdb -load $HOME/.Xresources xsetroot -solid gray & xclock -g 50x50-0+0 -bw 0 & xload -g 50x50-50+0 -bw 0 & xterm -g 80x24+0+0 & xterm -g 80x24+0-0 & twm Sites that want to create a common startup environment could simply create a default .xinitrc that references a site-wide startup file: #!/bin/sh . /usr/local/lib/site.xinitrc Another approach is to write a script that starts xinit with a specific shell script. Such scripts are usually named x11, xstart, or startx and are a convenient way to provide a simple interface for novice users: #!/bin/sh xinit /usr/local/lib/site.xinitrc -- /usr/bin/X -br ENVIRONMENT VARIABLES
DISPLAY This variable gets set to the name of the display to which clients should connect. XINITRC This variable specifies an init file containing shell commands to start up the initial windows. By default, .xinitrc in the home directory will be used. FILES
.xinitrc default client script xterm client to run if .xinitrc does not exist .xserverrc default server script X server to run if .xserverrc does not exist SEE ALSO
X(7), startx(1), Xserver(1), Xorg(1), xorg.conf(5), xterm(1) AUTHOR
Bob Scheifler, MIT Laboratory for Computer Science X Version 11 xinit 1.3.2 XINIT(1)
All times are GMT -4. The time now is 12:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy