MAE 2.0 License Manager & "su" Command in Solaris 2.4 (12/95)

The license manager in MAE does not seem to let the use of the "su" command switch to a licensed MAE account.

For example, create two accounts on a SPARCstation, calling one "works" and the other "doesnt". Use the license manager and give "works" access to use MAE. Then if you login with the "works" account, MAE functions as it should. However, if you login with "doesnt" account and enter "su - works", your environment changes to the "works" account, but you will not be able to run MAE.

Is there a workaround for this other than having to log out and log back in as the other user?
We were able to run MAE with the "su - username" command successfully with the following extra settings before launching MAE under Solaris 2.4, as a reference we followed your example above:

Step 1
------
Login as "doesnt" from the initial Solaris Login session

Step 2
------
Launch /usr/openwin/bin/openwin

Step 3
------
Create two "cmdtool" windows, for example, cmdtool.1 and cmdtool.2

Step 4
------
On the cmdtool.2 window, enter the command:

% su - works

Then set the DISPLAY environment variable, and export it.

% DISPLAY=sparc5:0.0; export DISPLAY

Step 5
------
On the cmdtool.1 window, you need to disable X server access control, or assign server access to a host. In Solaris 2.4 by default the X server access control is enabled, and no hostname is authorized to run ANY X program EXCEPT running from the initial login shell. Therefore you need to use "superuser" to explicitly grant access or disable access control with one of the following commands:

% su (as a super user)
# /usr/openwin/bin/xhost + (disable access control)

Step 6
------
On the cmdtool.2 window, you can now launch MAE with the MAE binary full path, example command:

% /opt/apple/bin/mae


NOTE: In HP-UX by default the X server access control is also enabled, but the "localhost" and the real local hostname, for example "hp715", are automatically authorized by the X server. Therefore you do not have to run "xhost" to assign access for your local workstation.


Support Information Services
Published Date: Feb 19, 2012