T.R | Title | User | Personal Name | Date | Lines |
---|
1613.1 | | MELTIN::dick | Gvriel::Schoeller | Fri Oct 20 1989 14:00 | 13 |
| If you define DECW$USER_DEFAULTS in LOGIN.COM and DECW$LOGIN.COM to be
something other than SYS$LOGIN it will work for all files that are read
in after that in that process (most applications). It will not affect
defaults read in by the session manager, decwindows window manaager or
decw$terminal controller process. These do not execute LOGIN.COM.
Therefore, DECW$XDEFAULTS.DAT, DECW$SM*.DAT and DECW$TERMINAL_DEFAULT.DAT
must remain in SYS$LOGIN.
You can redefine the above with a simple DEFINE. You might want to
DEFINE/JOB for better support of sub-processes.
Dick
|
1613.2 | > 1613.1 | ZUR01::BRUGGER | Hansjoerg Brugger @RLE, CH | Fri Oct 20 1989 14:22 | 5 |
| Thanks for the fast answer.
regards
Hansjoerg
|
1613.3 | Another idea... | CIM::KAIRYS | Michael Kairys | Tue Oct 24 1989 13:00 | 14 |
| It appears that most Well-behaved DECwindows applications look for
resource definition files first in DECW$SYSTEM_DEFAULTS: and then in
DECW$USER_DEFAULTS:. Now, DECW$SYSTEM_DEFAULTS: is actually a
searchlist of three directories:
"DECW$SYSTEM_DEFAULTS" = "SYS$COMMON:[DECW$DEFAULTS.USER]"
= "SYS$COMMON:[DECW$DEFAULTS.SYSTEM]"
= "SYS$LIBRARY:"
One approach I have taken to avoid cluttering up my SYS$LOGIN is to put
files in SYS$COMMON:[DECW$DEFAULTS.USER], which is normally empty. Note
that this does not offer per-user customization, more like a place to
put modified files without danger of purging away the originals.
|
1613.4 | Not a good idea | MELTIN::dick | Gvriel::Schoeller | Tue Oct 24 1989 13:26 | 13 |
| .3
Michael,
SYS$COMMON:[DECW$DEFAULTS.USER] is where applications which are not part of
the core set put their .UID and .DAT files. Therefore, this is not a very
good habit to get into. If you want to have a safe place for them that won't
need to be reset every time you login and into which you can put ALL .DAT
files, I might suggest that you set your UIC group unique from others on
your system and define a group logical at boot time.
Dick
|
1613.5 | Another view on the same question | QUICHE::PITT | Suspend all hackers ... by the neck! | Fri Oct 27 1989 05:35 | 26 |
| Being a tidy sort of individual, I like to keep my top level directory
containing as little as possible - the ideal would be for it to contain only
(sub-)directories. There are other users around here with the same views. I
can move most DECwindows files with the logical given earlier, but I would like
to move them _all_. I too would like a per-user method of redirecting
DECW$USER_DEFAULTS.
What chance of it (one day) being made to work that if that logical points only
to a sub-directory (e.g. [.DECW]) that this hangs off the user's own default
directory? (I'm assuming that this doesn't actually work at the moment ...)
That way everything could be moved out of the top-level directory for all users.
Let's see how that would work in practice: the system manager would define a
logical DECW$USER_DEFAULTS_DEFAULTS to be "[.DECW]" followed by "" - two trans-
lations for the logical. When the session manager starts, after it learns the
user's context, it defines the logical DECW$USER_DEFAULTS to a suitable value,
in exec mode in the process table. If my Sys$Login translates to
Disk$Users:[Pitt], then it would make Disk$Users:[Pitt.Decw] if that directory
exists, and Disk$Users:[Pitt] otherwise. Users would still be able to define
their own DECW$USER_DEFAULTS pointing somewhere completely different if they
wished, from their own Login.Com.
How does this seem to other people?
T
|
1613.6 | | LESLIE::LESLIE | Andy ��� Leslie | Fri Oct 27 1989 07:11 | 7 |
| Try putting this in your systems DECW$SYLOGIN.COM. Note that it only
works for single rooted accounts - ie if your default directory is
defined multiply like [SYSMGR] it has to be hard coded.
$Login_ == f$element(0,"]",f$trnlnm("SYS$LOGIN"))
$Define DECW$user_defaults "''login_'.decw$user_defaults]"
|
1613.7 | Thanks for the suggestion, Andy ... | QUICHE::PITT | Suspend all hackers ... by the neck! | Fri Oct 27 1989 07:19 | 7 |
| Thanks for .6. Unfortunately, I suspect that even DECW$SYLOGIN is still too
late for this definition. Surely by then the SM is already started, which means
that DECW$SM.LOG has already been created ... Also the Color and General setup
files have already been read, haven't they?
T
|
1613.8 | ULTRIX equivalents to DECW$*_DEFAULTS? | AIRBAG::SWATKO | Electrons are cheap. Trees are not. | Wed Feb 07 1990 15:51 | 8 |
| This is probably covered elsewhere but I can't find it.
What is the ULTRIX equivalent to VMS logical DECW$SYSTEM_DEFAULTS?
How about the ULTRIX equivalent to VMS logical DECW$USER_DEFAULTS?
Thanks,
-Mike
|
1613.9 | | VIA::FINNEGAN | All of the best intentions are less than one good act. | Fri Feb 09 1990 09:15 | 11 |
| There are no logicals on Ultrix.
The location of the system defaults files is:
/usr/lib/X11/app-defaults
and the location of the user defaults files is you login directory.
I do not think there is any wat of redirecting these areas (aside from links
whihc probably don't do what you want).
Neal
|
1613.10 | | PRSIS4::WDAVIES | Winton Davies @EVO DTN:858-5764 | Wed Apr 04 1990 11:02 | 11 |
| re .6 and .7
I'm having the same problems - I can get all but my SM etc files into
my subdirectories - and I'm annoyed - I'd really like to have _all_
my DECW$ files down there.
So is .6 true or not, and if it isn't has anyone got any further with
this (like a DECW$LGICMD field in the SYSUAF(or why not use the SYSLGI
field (that would be a start!) ?
Winton
|