Create/rebuild a new .Xauthority file


This document describes the procedure for rebuilding a /$HOME/.Xauthority file. The information in this document applies to AIX 5.1 and higher.


If you get an MIT magic cookie error when trying to gain remote access the CDE or Xdm, you may be able to solve the problem by rebuilding the .Xauthority file in the home directory of the user trying to log in.

Follow these steps to create a /$HOME/.Xauthority file.

Log in as user and confirm that you are in the user's home directory.


Rename the existing .Xauthority file by running the following command

mv .Xauthority old.Xauthority


Generate a new .Xauthority file by running the following command:

xauth generate :0 . trusted


At the command line, create a new magic-cookie key by entering the following:

randomkey=`/usr/bin/ksh -c 'echo $(( $RANDOM * $RANDOM * 2 ))'`


Add a new entry for another server by running the following command:

xauth add ${HOST}:0 . $randomkey


To view a listing of the .Xauthority file, enter the following

xauth list

Comments

Post a Comment

Popular posts from this blog

Installing and configuring the storage agent (AIX)

The storage agent must be installed on a client system that has connections to storage resources on the SAN. Before beginning this procedure: Verify that your system meets the hardware and software requirements. Be sure that you have the information recorded in the configuration-information work sheets. Close all existing Tivoli® Storage Manager products prior to installing the storage agent. Installation will stop if an active Tivoli Storage Manager process is detected. If this occurs, close all active Tivoli Storage Manager products and retry installing the storage agent. The storage agent honors the Tivoli Storage Manager server environment variables DSMSERV_CONFIG. The instructions in this section are shown using the Software Management and Installation Tool (SMIT). You can also use the Install and Update Software Manager (installm). To reduce workload and processing time and to optimize LAN-free performance, do not install the storage agent and the Tivoli Storag...
Read more

Move a file system to another volume group

How to move FS to anotherVG UNMOUNT fs Copy the source logical volume to the desired volume group with the cplv command. For example, where myvg is the new volume group and mylv is the name of the user's logical volume, enter:        cplv -v myvg mylv This will return the name of the new logical volume, such as lv00. 2- To make a new JFS log, enter the following command, where myvg is the name of the new volume group, enter:        mklv -t jfslog  myvg 1 To make a new JFS2 log, enter:      mklv -t jfs2log  myvg 1 ** This new logical volume will need to be formatted with the logform command in order to function properly as either a JFS or JFS2 log. For example:        logform /dev/loglv00 Answer yes to destroy. 3-Change the filesystem to reference a log device that exists in the new volume group and the new logical volume with the chfs command. For example, where ...
Read more

Xclock does not work after switch to another user

suppose that user1 can run xclock and after switch to user2 xclock does not work does not matter if user1 or user2 is root you need to import the following values from user1 to user2 For KSH Shell $user1:/> xclock $user1:/>su - user2 $user2:/> xclock Error: Can't open display: $user2:/>exit  $user1:/>xauth list hostname/unix:10  MIT-MAGIC-COOKIE-1  630b2e7a7a794022834b0783b6f471fa hostname/unix:11  MIT-MAGIC-COOKIE-1  dbdcd6d69b9b3002484c4ea1e29a2ad5 hostname/unix:12  MIT-MAGIC-COOKIE-1  745ca626d4ef81101ef744589b4cfb09 $user1:/>echo $DISPLAY localhost: 11.0   (Hint : choose the matching values)  $user1:/>su - user2  $user2:/>xauth add hostname/unix:11  MIT-MAGIC-COOKIE-1  dbdcd6d69b9b3002484c4ea1e29a2ad5   $user2:/>export DISPLAY=localhost:11.0 $user2:/> xclock For CSH Shell $user2:/>xauth add hostname/unix:11  MIT-MAGIC-COOKIE-1  dbdcd6d69...
Read more