Sponsored Content
Full Discussion: [Solved] Xmanager on HP-UX
Operating Systems HP-UX [Solved] Xmanager on HP-UX Post 302494390 by beayni33 on Monday 7th of February 2011 06:27:33 AM
Old 02-07-2011
i am using HP 11.31
and yes i have thsi directory : /usr/bin/X11 and containing programs such as "xterm"

On the HP-UX server (as root) do you get an error for these enquiries:?
NO
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Xmanager

Hi All, I am a real newbie to this so forgive me if I ask anything which may sound silly. I have a SunFire V1120 installed with Solaris 8 on it. I have Xmanager loaded onto my pc and i want to use this to connect to this box. However Xmanager doesn't recognise the box, but I can telnet to it no... (1 Reply)
Discussion started by: joe27
1 Replies

2. Solaris

Xmanager

hi everybody want to access a SOLARIS system with an X Client ( or server ) ( Called Xmanager)...i think all xclients opearate the same way. Problem : i have the error Xdmcp connection failed when i launch it! help please! PS: all i have done is just giving Xmanager the IP of the... (4 Replies)
Discussion started by: hmaiida
4 Replies

3. UNIX for Dummies Questions & Answers

Xmanager UNIX HP_OpenView

***** I running Solaris 9 and Xmanager 2.0 ***** Hey guys, Newbie question... I'm trying to get HP OpenView's X Windows GUI to load on my WinXP machine. I know another guy at work is running Xmanager 1.3 (I have 2.0) and when he types ovw& on the server it loads the OpenView GUI on his... (4 Replies)
Discussion started by: kingdbag
4 Replies

4. Linux

Xmanager

I am unable to view the GUI mode of the Fedora Linux machine through the Xmanager. I don't have issues in viewing my Solaris boxes. Please let me know if anything needs to be done about this? (3 Replies)
Discussion started by: chrisanto_2000
3 Replies

5. UNIX for Dummies Questions & Answers

Xbrowser/Xmanager question

In the Xbrowser window, under status column, i see the following: 2 users, load: 3.7, 3.7, 3.7 What does "load" mean exactly, and the three numbers? Thanks! (4 Replies)
Discussion started by: Deanne
4 Replies

6. Linux

xmanager

For remote console logging purpose we use X-manager for Solaris environment. How X-manager config for Linux systems. I want to get Linux desktop to remote pc. that is not ssh or telnet. Please help me. (0 Replies)
Discussion started by: saga499
0 Replies

7. Shell Programming and Scripting

How to force Xmanager to execute .profile?

hello all i created a login scrip and add it successfully to .profile now i need to force this .profile to be executed if the user login using xmanager not a normal telnet best regards ---------- Post updated at 09:05 AM ---------- Previous update was at 03:25 AM ---------- Ant updates ???? (10 Replies)
Discussion started by: islam.said
10 Replies

8. Solaris

Java Application slowness with Xmanager

Hi! I have a m3000 server with solaris 10. Clients connecting to server using Xmanager. But when they open a Java based application its very slow and some times hanging. But when I tried with VNC it works fine. Is this a BUG in Xmanager? Or Is there any method to solve this? Thanks, Charith (3 Replies)
Discussion started by: charith.upendra
3 Replies

9. AIX

Console redirect to xmanager in AIX ?

Hello, Oracle PDF reports run only when you run the command # xhost + from the console, but if you run from the xmanager session , then report doesn't work running from windows pc using xmanager # xhost + access control disabled, clients can connect from any host # echo... (7 Replies)
Discussion started by: filosophizer
7 Replies

10. Solaris

Xmanager 4 not able to connect to Solaris11

I am trying to connect via Xmanager 4 to a T4-2 server running Solaris 11. I checked the /etc/gdm.custom.conf file. The error I get is The MAC (Message Authentication Code) of packet is incorrect When I start the Xmanager on soalris I get a message /dev/fb (file or directory) does not... (2 Replies)
Discussion started by: Maqsood Mohamme
2 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 05:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy