| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3441.1 | | UTRTSC::HELDEN | If you can't hear it, you better C it | Tue Oct 09 1990 10:41 | 16 |
| Create on the workstation you want to display on the following file:
sys$manager:decw$server_access_allowed.dat
Write on the top of that file
* * *
Meaning Transport Node Username.
The rules for displaying remain the same.
Now the server will display all client windows on the login screen,
beware that there is no window-manager running then.
Success
another Mark
|
| 3441.2 | Warning however... | IO::MCCARTNEY | James T. McCartney III - DTN 381-2244 ZK02-2/N24 | Wed Oct 10 1990 11:47 | 9 |
|
Be advised however that this means that ANY client from ANY node can
access the same display.
If you want to restrict the access rights, you can explicitly list
the nodes and users in the file rather than just "* * *".
James
|
| 3441.3 | ??? | WIDGIT::WEST | SCARY : A programmer with a screwdriver. | Wed Oct 10 1990 18:51 | 6 |
|
and for Ultrix... ?????
-=> Jim <=-
|
| 3441.4 | | DECWIN::FISHER | I like my species the way it is" "A narrow view... | Thu Oct 11 1990 15:35 | 4 |
| I don't think there is a default security file in Ultrix is there? You can
use Xhost, but that has to be done after each reset.
Burns
|
| 3441.5 | /etc/Xn.hosts | MIPSBX::thomas | The Code Warrior | Thu Oct 11 1990 23:26 | 1 |
| where n is the display number. Each line is either a IP or DECnet host.
|
| 3441.6 | | MSBCS::SKI | | Fri Oct 12 1990 13:28 | 14 |
| Sorry, but I can't get this to work.
I created the file:
SYS$SYSDEVICE:[SYS21.SYSMGR]SYS$MANAGER:DECW$SERVER_ACCESS_ALLOWED.DAT
Contenets of file is:
* * *
I still get "connection refused by server" messages when I do:
$ SET DISPLAY/CREATE/NODE=workstation
$ RUN SYS$SYSTEM:DECW$PUZZLE
Do I need to reboot or restart DECwindows in order to make it take effect?
|
| 3441.7 | Ah, now it's working for me | MSBCS::SKI | | Fri Oct 12 1990 15:43 | 10 |
| Hmmmmm....I logged into the workstation and then logged out.
Now the access_allowed file has taken effect and I can display
to vacant workstation.....neato.
(Sorry for the false alarm)
However, without a window manager running you are extremely restricted
in what you can do with the application you are displaying. And that
darn login box stays in the way.
Ah well, It is still interesting that it can be done.
|
| 3441.8 | get rid of WSAn | VINO::MCARLETON | Reality; what a concept! | Mon Oct 15 1990 10:59 | 17 |
|
You can start a remote window manager from some other system to allow
you to manage windows on your server.
If you stop the WSAn process on the remote system, the login window
will disappear. I was thinking of writing an application that would
put up a small box on the screen with a push button that says "Push
here to login". Pushing the button would start the normal login
application. This would allow remote applications to use the screen
without the login process getting in the way.
It would be better if there was some way to tell the server "please
drop all login connections for the remote application that wants to
use the screen." The login application would have to have some kind
of window property to allow the server to recognize it.
MJC
|