Sponsored Content
Operating Systems AIX Installed AIX6.1 in LPAR, but fail to start xclock Post 302497733 by wingcross on Thursday 17th of February 2011 11:42:47 PM
Old 02-18-2011
Hi AixCraft,

Not sure what I did, my team mate reboot the LPAR, we can launch the xclock. I wonder if it has something to do with the ethenet settings I did earlier that affect the command EXPORT DISPLAY ??.

I check again using ps, X was not running. I didnt enable the X11 forwarding.

Anyway, thanks for your help Smilie
 

10 More Discussions You Might Find Interesting

1. Solaris

Unable to run xclock

Hello. I am trying to run xclock on newly built solaris box - These are the steps I followed: # DISPLAY=localhost:0.0 # export DISPLAY # xclock xclock: not found # cd /usr/openwin/bin # ./xclock Error: Can't open display: localhost:0.0 # Please suggest, what am i doing wrong? Thank... (27 Replies)
Discussion started by: panchpan
27 Replies

2. Shell Programming and Scripting

Xclock and background

Hi everyone, could you explain why am I not able to bring up xclock, or for that matter any Xtools (xcalc etc...), in the background? When I execute: xclock & This brings up the clock in the foreground, my focus is on the clock, not back in my command window. Any suggestion? ... (2 Replies)
Discussion started by: gio001
2 Replies

3. AIX

DCE fail to start Initial Directory server - help

Guys I am having a problem starting one of the DCE Servers known as Initial Directory server . All other process are running ecxept these one Master server Configured Running Security client Configured Running RPC ... (1 Reply)
Discussion started by: Aix|Dr
1 Replies

4. AIX

LPAR freezes after switching of storage (lpar is mirrored)

Hi all, I have the following configuration 2 ds3524 storage disk systems located over 2 locations 2 P720 server located over 2 locations DS3524 are connected to san switch. Each vio server has 1 fc adapter attached to a san switch. per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies

5. Red Hat

Trouble with installed / not installed rpm unixODBC/libodbc.so.1

Hey there, i run 1: on my server (RHEL 6) and getting response that the libodbc is not installed. If i use yum for installation, it tells me, there is no package like this ( 2: ). Since in the description of Definiens is mentioned that the Run-time dependency is unixODBC (libodbc.so.1), I assume... (2 Replies)
Discussion started by: rkirsten
2 Replies

6. Solaris

Xclock help

This is where I am getting stuck and I am wondering if I can get some help from the community. I log into putty with X11 forward enable echo $DISPLAY DISPLAY=localhost:10.0 export DISPLAY xclock ( I do see a clock) :) I am happy that I finally get to install Oracle 11g on solaris... (2 Replies)
Discussion started by: newborndba
2 Replies

7. Red Hat

Xclock command not working

Hi, I am using Xming tool to open the my RHEL machine remotely in UI mode. When I use xclock command using 'root', the command works properly and I can see the clock pop-up. However, when I run the 'xclock' command using oracle user I get an error, which is shown in the attached file. Can... (6 Replies)
Discussion started by: omniok
6 Replies

8. AIX

How to differentiate between a standalone LPAR and a VIOC (which again is a lpar)?

There can be configurations in IBM Server wherein a standalone partition is created on some supported IBM Server Or A VIOS - VIOC LPARs created. Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..? On a... (2 Replies)
Discussion started by: Manish00712
2 Replies

9. AIX

Startx xclock on virtual lpar

Hello, Is there a way to run xclock or 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 on the AIX Lpar and run on it the... (2 Replies)
Discussion started by: filosophizer
2 Replies

10. UNIX for Beginners Questions & Answers

Bash find version of an installed application but if none is found set variable to App Not Installed

Hello Forum, I'm issuing a one line bash command to look for the version of an installed application and saving the result to a variable like so: APP=application --version But if the application is not installed I want to return to my variable that the Application is not installed. So I'm... (2 Replies)
Discussion started by: greavette
2 Replies
routeadm(1M)															      routeadm(1M)

NAME
routeadm - IP forwarding and routing configuration SYNOPSIS
routeadm [-p] routeadm [-R root-dir] [-e option...] [-d option...] [-r option...] [-s var=value] routeadm [-u] The routeadm command is used to administer system-wide configuration for IP forwarding and routing. IP forwarding is the passing of IP packets from one network to another; IP routing is the use of a routing protocol to determine routes. routeadm is used to enable or disable each function independently, overriding any system default setting for each function. The first usage, above, reports the current configuration. The following command-line options are supported: -p Print the configuration in parseable format. -R root-dir Specify an alternate root directory where routeadm applies changes. This can be useful from within JumpStart scripts, where the root directory of the system being modified is mounted elsewhere. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). -e option... Enable the specified option. -d option... Disable the specified option. -r option... Revert the specified option to the system default. The system defaults are specified in the description of each option. -u Apply the currently configured options to the running system. Enable or disable IP forwarding, and/or launch or kill routing daemons. It does not alter the state of the system for those settings that have been set to default. This option is meant to be used by adminis- trators who do not want to reboot to apply their changes. -s var=value Specify string values for specific variables in a comma-separated list with no intervening spaces. If invalid options are specified, a warning message is printed and the program exits. The following variables can be specified: ipv4-routing-daemon=<full_path_to_routing_daemon> Specifies the routing daemon to be started when ipv4-routing is enabled. The routing daemon specified must be an executable binary or shell-script. Default: "/usr/sbin/in.routed" ipv4-routing-daemon-args=<args> Specifies the startup arguments to be passed to the ipv4-routing-daemon when ipv4-routing is enabled. Default: no arguments ipv4-routing-stop-cmd=<command> Specifies the command to be executed to stop the routing daemon when ipv4-routing is disabled. <command> may be an executable binary or shell-script, or a string that can be parsed by system(3C). Default: "kill -TERM `cat /var/run/in.routed.pid`" ipv6-routing-daemon=<full_path_to_routing_daemon> Specifies the routing daemon to be started when ipv6-routing is enabled. The routing daemon specified must be an executable binary or shell-script. Default: "/usr/lib/inet/in.ripngd" ipv6-routing-daemon-args=<args> Specifies the startup arguments to be passed to the ipv6-routing-daemon when ipv6-routing is enabled. Default: "-s" ipv6-routing-stop-cmd=<command> Specifies the command to be executed to stop the routing daemon when ipv6-routing is disabled. <command> can be an executable binary or shell-script, or a string that can be parsed by system(3C). Default: "kill -TERM `cat /var/run/in.ripngd.pid`" Note that, if you change the routing daemon and stop commands from their defaults, routeadm does not monitor these daemons or commands. This is because the status of these programs depends on user configuration. When non-default daemons or stop commands are in use, routeadm always returns a status of "unknown". Multiple -e, -d, and -r options can be specified on the command line. Changes made by -e, -d, and -r are persistent, but are not applied to the running system unless routeadm is called later with the -u option. Use the following options as arguments to the -e, -d, and -r options (shown above as option...). ipv4-forwarding Controls the global forwarding configuration for all IPv4 interfaces. The system default is disabled. If enabled, IP will forward IPv4 packets to and from interfaces when appropriate. If disabled, IP will not forward IPv4 packets to and from interfaces when appropriate. ipv4-routing Determines whether or not an IPv4 routing daemon is run. The system default is enabled unless the /etc/defaultrouter file exists, in which case the default is disabled. The routing daemon for IPv4 is /usr/sbin/in.routed. ipv6-forwarding Controls the global forwarding configuration for all IPv6 interfaces. The system default is disabled. If enabled, IP will forward IPv6 packets to and from interfaces when appropriate. If disabled, IP will not forward IPv6 packets to and from interfaces when appropriate. ipv6-routing Determines whether or not an IPv6 routing daemon is run. The system default is disabled. The routing daemon for IPv6 is /usr/lib/inet/in.ripngd. If not set, the system boot scripts' current default logic determines whether or not to run in.ripngd. Note that even if this option is enabled, an IPv6 routing daemon will run only if ipv6-forwarding is enabled. The forwarding and routing settings are related but not mutually dependent. For example, a router will typically forward IP packets and use a routing protocol, but nothing would prevent an administrator from configuring a router that forwards packets and does not use a routing protocol. In that case, the administrator would enable forwarding, disable routing, and populate the router's routing table with static routes. The forwarding settings are global settings. Each interface also has an IFF_ROUTER forwarding flag that determines whether packets can be forwarded to or from a particular interface. That flag can be independently controlled by means of ifconfig(1M)'s router option. When the global forwarding setting is changed (that is, -u is issued to change the value from enabled to disabled or vice-versa), all interface flags in the system are changed simultaneously to reflect the new global policy. Interfaces configured by means of DHCP automatically have their interface-specific IFF_ROUTER flag cleared. When a new interface is plumbed by means of ifconfig(1M), the value of the interface-specific forwarding flag is set according to the cur- rent global forwarding value. Thus, the forwarding value forms the "default" for all new interfaces. The following exit values are returned: 0 Successful completion. !=0 An error occurred while obtaining or modifying the system configuration. Example 1: Enabling IPv4 Forwarding IPv4 forwarding is disabled by default. The following command enables IPv4 forwarding: example# routeadm -e ipv4-forwarding Example 2: Apply Configured Settings to the Running System In the previous example, a system setting was changed, but will not take effect until the next reboot unless a command such as the follow- ing is used: example# routeadm -u Example 3: Making a Setting Revert to its Default To make the setting changed in the first example revert to its default, enter the following: example# routeadm -r ipv4-forwarding example# routeadm -u Example 4: Starting in.routed with the -q Flag The following sequence of commands starts in.routed with the -q flag: example# routeadm -s ipv4-routing-daemon-args="-q" example# routeadm -u See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ ifconfig(1M), in.routed(1M), gateways(4), attributes(5) 8 Apr 2005 routeadm(1M)
All times are GMT -4. The time now is 03:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy