Startx xclock on virtual lpar

Tags
aix, faq, xclock, xwindows

 
Thread Tools Search this Thread
# 1  
Old 09-21-2018
Startx xclock on virtual lpar

Hello,

Is there a way to run
Code:
xclock

or
Code:
startx

on LPAR, since LPAR doesn't have any console or it is connected to HMC


usually the way is to export the display to some PC which has Xmanager running on it, but in my case, I want to run xmanager [startx] on the AIX Lpar and run on it the xclock

In the attachment,

the ones that show localhost
Code:
root@oradb:/>echo $DISPLAY
10.1.1.71:1.0

while on cloapp, it shows
Code:
root@oradb:/>echo $DISPLAY
support:0.0

support is = 10.1.1.71


How can I make CLOAPP same as oradb (which is localhost on the XMANAGER )
Startx xclock on virtual lpar-xmanager-png

Last edited by filosophizer; 09-21-2018 at 10:57 AM..
# 2  
Old 09-21-2018
getting this error
Code:
X connection to  hostname:0.0 broken (explicit kill or server shutdown)


Last edited by RudiC; 09-21-2018 at 06:08 PM..
# 3  
Old 09-21-2018
Quote:
Originally Posted by filosophizer
Is there a way to run
Code:
xclock

or
Code:
startx

on LPAR, since LPAR doesn't have any console or it is connected to HMC
I have (in a cursory way) described how XWindows works already here but you might profit from me expanding on that a bit:

XWindows is a complete networked system for working with graphically oriented programs. In fact it is more a client/server-oriented protocol (like, i.e. ftp) rather than a piece of software.

On one hand you have some graphical display - a graphics adapter attached to a system and a screen capable of graphical output (for the sake of simplicity we will voluntarily leave out multi-screen displays and other complicated things for now). This is called an X-server, because it provides certain capabilities whcih can be used by clients. In fact an X-server is a piece of software which manages this piece of hardware. Think of it as a networked graphics driver.

On the other hand there are programs being able to use the capabilities such an X-server provides: these are called X-clients. Notice that the X-server usually runs on the client machine (the one you sit in front of) and the X-client runs on the server system (i.e. a machine in the data centre). This can be a bit confusing at first, but actually from the role the various software pieces are playing - here a pice that provides some service, there a piece that makes use of this service - it makes perfect sense.

In between these two programs there needs to be a network connection (except for the special case where they are running on the same system) and in fact XWindows has its own transport protocol: X-protocol (now, who'd have thought this is its name?). X-protocol per default uses port 6000.

This is what you need the DISPLAY-variable for: it tells the X-client (in your case: xclock which server to use to display itself. There could be more than one server in the network. The DISPLAY-variable has the following format:

<FQDN>:<Display-Nr>.< Screen-Nr>

i.e.: myclient.somecompany.com:0.0 means: use the X-server on myclient.somecompany.com for output and display it on the first screen (screen 0) of the first display (display 0). A system could have several displays attached and each display could consist of several screens, hence the numbers. So you set the DISPLAY-variable in the environment of the X-client process first, then start the X-client. The X-server has to run already for this.

Now, an X-server might not want to allow every client to use it, so there is some sort of access control. This is what the program xhost is for. I suggest to carefully read its man-page, but for test purposes we can simply switch off any access control with:

Code:
# xhost +

Nota bene: you do this on the X-servers side, because having access control only makes sense on the system where the X-server runs. Now (and given that no firewall interferes with port 6000) it should work.

I hope this helps.

bakunin

|
Thread Tools Search this Thread
Search this Thread:
Advanced Search

More UNIX and Linux Forum Topics You Might Find Helpful
LPAR missing virtual interface max AIX 7 3 Weeks Ago 03:15 AM
How to differentiate between a standalone LPAR and a VIOC (which again is a lpar)? Manish00712 AIX 2 07-17-2015 05:40 PM
Xclock command not working omniok Red Hat 6 01-12-2015 07:32 AM
VIOS: Extend virtual disk assigned to running lpar? j_aix AIX 2 08-19-2014 03:35 PM
Xclock help newborndba Solaris 2 04-22-2014 05:35 PM
xclock comand not found jsynodin Red Hat 1 07-24-2012 02:28 PM
Adding Virtual Adapter to LPAR audis$ AIX 5 11-16-2011 12:10 PM
LPAR freezes after switching of storage (lpar is mirrored) markiemark AIX 2 03-10-2011 06:08 PM
How to open multiple virtual terminals to a single LPAR wingcross AIX 1 02-22-2011 11:14 AM
Installed AIX6.1 in LPAR, but fail to start xclock wingcross AIX 5 02-18-2011 05:08 AM
xclock not working in HP-Unix 11.23 narayanv HP-UX 1 06-29-2010 10:44 AM
Xclock and background gio001 Shell Programming and Scripting 2 03-05-2009 01:02 PM
Unable to run xclock panchpan Solaris 27 11-14-2008 08:53 AM
LPAR processor/virtual processor settings guttew AIX 1 02-01-2007 01:52 PM
Help urgent : vio server - add extral disk on virtual lpar touny AIX 0 08-01-2005 08:05 PM