Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
******************** Overview ******************** I have an X windows application which calls X$OPEN_DISPLAY(0). a) If the application is started from a DECterm process, no problem... X$OPEN_DISPLAY completes successfully, and the windows are correctly displayed on the workstation monitor. b) If user X is logged into the workstation (from the workstation monitor), and user X also logs into the workstation from a VTxxx terminal, the application can be started from user X's VTxxx process and the windows are displayed on the workstation monitor. ******************** Problem ******************** If user X is logged into the workstation (from the workstation monitor), and user Y logs into the workstation from the VTxxx, user Y can not start the application. The call to X$OPEN_DISPLAY(0) results in the following error... Xlib: connection to "<node>::0.0" refused by server Xlib: Client is not authorized to access server I tired giving user Y permission to open the display by adding the following to the Customize Security menu, but nothing seemed to help: NODE USERNAME TRANSPORT ------- -------- --------- <NODE> Y DECNET <NODE> Y LOCAL <NODE> Y * Can anyone tell me what I'm doing wrong? Thank-you.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2621.1 | Local node is referred to as node '0' | STAR::VATNE | Peter Vatne, VMS Development | Tue Apr 17 1990 19:57 | 4 |
Try using nodename '0' instead of your node name. This is a rather hacky way of specifying your own node. I'd like to get rid of it as it obviously causes confusion. However, it is embedded in all of our transports, so removing this might not be very easy. | |||||
2621.2 | Thanks. | FORTSC::KISHIMURA | Wed Apr 18 1990 15:37 | 5 | |
Thank-you. That solved the problem. I have to agree though, it is not very intuitive. It might also be nice if this little fact were documented in the manuals. Anyway, thanks again. | |||||
2621.3 | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Thu Apr 19 1990 13:18 | 5 | |
For future readers of this conference, if you look in the server log when something like this happens, it will tell you what it thinks the node and user names are when a connection is rejected. SYS$MANAGER:DECW$SERVER_0_ERROR.LOG. Burns |