| 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 |
Hello everybody - here another window problem:
A customer of mine wants to start an application, which uses the
decwindow-session manager systemwide for all users that login.
If he tries to do this in decw$login the application doesn't run,
because the sessionmanager starts after his application is startet.
Furhter on he must write the startup commando for his procedure
to every decw$login of his users.
So is there a way to solve it systemwide? - Please be patient with
me I'm not so firm in decwindows !!
Many thanks in advance
Olaf
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2259.1 | STAR::MCLEMAN | Jeff McLeman, VMS Development | Tue Feb 13 1990 09:49 | 3 | |
Try SYS$MANAGER:DECW$SYLOGIN.COM This gets executed by every session startup on the system. | |||||
| 2259.2 | BOMBE::MOORE | Eat or be eaten | Tue Feb 13 1990 20:15 | 8 | |
You can delay your application startup to allow time for the session
manager to initialize. I use something like this in DECW$SYLOGIN.COM:
$ Spawn/NoWait/Input=dev:[dir]run_my_app.com Wait 0:01:00
Perhaps someone can offer a reliable method of determining when the
session manager is ready. I used to watch for the DECterm controller's
mailbox, but that doesn't work if a DECterm is not being autostarted.
| |||||