| 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 |
Hi,
there have already been so many discussions about this silly captive
application theme, I'm so sorry, either I'm too stupid or the pre
originators haven't tested their versions which all "should work".
I'm trying about 3 days to manage the following:
1. log into an account where only the start of one single
application within e.g. the DECW$LOGIN file should be invoked
("log in" means that there was the login mask of DW before)
2. The application starts. After ending it, the login mask (digital
logo and username/password should reappear.
So fine, so far. Works as assumed, but if quitting/exiting e.g. the
clock, an empty icon box remains and the pointer stays in wait state.
I tried it with many versions of the follwing two files and for test
purposes I had all priv's/defpriv's.
SYS$LOGIN:DECW$LOGIN.COM:
$ run/detach/auth/inp=comfile/out=nl: sys$system:dcl
$ logout
SYS$LOGIN:COMFILE.COM:
$loop:
$ pid = F$PID (context)
$ IF pid .EQS. "" THEN GOTO a_ok
$ IF F$GETJPI (";;pid'","PRCNAM") .EQS. "DECW$Clock"
$ THEN
$ stop/id='pid' !Already running, as we don't know why, kill it
$ ENDIF
$ goto loop
$a_ok:
$ set proc/name="DECW$Clock"
$ set display/create/node=0/transport=local
$ mc decw$clock
$ set process/priv=cmkrnl
$ run sys$system:decw$startlogin
$ exit
What am I doing wrong? Every time I have to restart the server
manually. I think there is a big bug in my thoughts.
Thanks in advance for observing my problem.
Armin
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3646.1 | Hmmm... | WIDGIT::WEST | SCARY : A programmer with a screwdriver. | Tue Nov 13 1990 10:19 | 18 |
Normally you choose the 'quit' option from the session manager. This does a server reset. You essentially want/need to do the same thing. I'm not sure if there is a way to do programmatically. You may end up doing something like: @SYS$MANAGER:DECW$STARTUP RESTART to restart the server every time. It sounds like you are trying to circumvent the session manager which is probably not very wise, without providing the same functionallity elsewhere. -=> Jim <=- | |||||
| 3646.2 | FRSTSC::ERLEMANN | Bedman strikes back | Wed Nov 14 1990 05:17 | 21 | |
Thanks Jim for reply, I tried that @SYS$MANAGER:DECW$START RESTART, but it seems that it won't work from a command procedure - only interactive. Another effect I was humbling over, was that the message number 02DBA002 appeared after restarting the server manually over net. (Probably there are server retry limit problems on my cpu (V2000 standalone, RD54, 14MB, VMS 5.4). I naturally could click this away via the traditional CTRL/F2 method... But the last hurdle we have to jump over is the automatic server restart. Is this or is this not supported? Customers are getting quite nervous because of their 'secure environment'. I know, I know, there have already been many discussions 'bout that -> we don't have to expect any convenient security within a DW environment... Finally; is it possible to restart the server via a procedure? Regards Armin | |||||
| 3646.3 | Kill the window manager | VINO::MCARLETON | Reality; what a concept! | Wed Nov 14 1990 10:41 | 9 |
It sounds like you forgot to kill the window manager application. The
server should go through the server reset when the last connection to
the server is closed. The window manager is the last application in
your case. The process that needs to be killed is DECW$WM_n where
'n' is the unit number of the 'WSAn:' pseudo workstation device defined
by the logical DECW$DISPLAY.
MJC
| |||||