[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

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

445.0. "format decw$server_access_*.dat?" by UTROFF::BROUWERS () Tue Mar 21 1989 08:05

    hi,
    
    can somebody tell me the format for the files 
    sys$manager:decw$server_access_*.dat ?
    i tried some things, like "decnet node user", "* * *" ,"decnet
    node/user" but nothing worked. 
    what is the clue ?
    
    thanks gerard brouwers swas holland
    

T.RTitleUserPersonal
Name
DateLines
445.1ASIA::MCLEMANJeff McLemanTue Mar 21 1989 09:567
When you did the format:

	transport node user

Did you restart the server? This must be done in order to pick up
changes.

445.2Can the file be commeneted?ATSEA::ELLISONThat is truly a wetbrain concept.Tue Mar 21 1989 10:543
	Can you use ! or something similar to comment DECW$SERVER_ACCESS_ALLOWED.DAT?

445.3still no solutionUTROFF::BROUWERSTue Mar 21 1989 13:444
    yes, i did restart the server, but still it does't work.
    may be you have an example ?
    

445.4it works....UTROFF::BROUWERSTue Mar 21 1989 14:0411
    hi,
    
    during my multiple exercises i tried a lot of things. i ended with
    the right string in the files, but with double quotes before and
    after the strings
    i changed it now and it works.
    thanks for your help.
    
    gerard.
    

445.5unix conventions (mostly)STAR::BRANDENBERGIntelligence - just a good party trick?Tue Mar 21 1989 14:503
    
    re .2:  The comment character is '#'.

445.6THRUST::LONGMon Mar 27 1989 05:2716
re: .0

    I don't know what your problem is but this always works for me:

     $ def/system decw$server_access_trusted/allowed <full file spec>
     $ the file contain the following:

     * * *


   Side note:  I'm only running the decwindows server when I do this,  I've
shot the session manager.


			paula

445.7Don't use * * *!DECWIN::FISHERBurns Fisher 381-1466, ZKO3-4/W23Tue Mar 28 1989 19:4515
    *PLEASE* everyone, be careful of * * *!!!  This means that ANYONE can
    write anything they like to your workstation screen while you are away.
    
    I won't spell out the exact scenario I have in mind, but it should not
    be too hard to imagine how one could steal information that the owner
    did not want stolen when this is the case.
    
    If you really want to do that, I certainly would not advertise the
    fact that I did it in a notes file!  Besides, it is much more
    sensible to figure out exactly what you want to allow and specify that.
    
    
    Burns
    

445.8your right of courseDOUBLE::LONGWed Mar 29 1989 00:3321
 Burns

  You have a good point,  I don't use (* * *) in the file either for VMS, 
 I was using it as an example.  Perhaps <transport type> <node_name> <username>
would have been a better choice.    

(I thinks this is how it works,  at least this is what I'm seeing) ---

   For what it's worth -- while your running the session manager the
access_allowed list (validlist) you specified  in the .dat file is replaced by
the access list the session manager maintains for you. When the session
manager comes up I believe it does a gethosts, then removes all the hosts in
the current validlist (removehosts).  After which the session manager will do
a set of addhosts (defines the local nodes and whatever the user specified). 
 
   Once the last client disconnects and the server resets, the user supplied
access_allowed list and access_trusted lists are re-built.


			paula

445.9decwindows rookieELRIC::MARSHALLhunting the snarkWed Apr 26 1989 17:3021
    Sorry to be so dense but I don't understand the answer to the original
    question, i.e. what is the correct format for these two files.
    
    I created the files and put in them the single line:
    
    * elric marshall
    
    when I restarted the server (@sys$manager:decw$server restart), the
    bloody thing does not restart but keeps flashing 
    
    	Message number 02DB821C
    
    in the operator window.
    
    Only when I do not have these files will the thing restart. What am I
    doing wrong?
    
    	thanks,
    
    	Sm

445.10STAR::BRANDENBERGSi vis pacem para bellumWed Apr 26 1989 17:5111
    
    The local node is (almost) always named "0", a bit of baggage
    deliberately inherited from DECnet's node zero.  There is not much
    point in using these files if you are using decw$startlogin/session
    manager to manager your workstation as they will overide the files
    (this is the source of the console message).  Also, loginout comes
    in under the SYSTEM account so something like "* 0 SYSTEM" should be
    in the trusted list.
    
    					monty

445.11Need system tooDECWIN::FISHERBurns Fisher 381-1466, ZKO3-4/W23Wed Apr 26 1989 17:526
It's easy to hang yourself with this stuff.  You MUST include * 0 SYSTEM
in the TRUSTED file, or Loginout can't ever come up.  These files replace
the default server values; they don't just add to them.

Burns

445.12thanksELRIC::MARSHALLhunting the snarkWed Apr 26 1989 21:018
Thanks, that seems to have done it.

                                                   
                  /
                 (  ___
                  ) ///
                 /

445.13something similar for ultrix?MINNIE::DOUGto bless and not to curseMon May 08 1989 17:598
    does something similar to this exist for ultrix?
    
    if not, is there anyway i can have an ultrix workstation sitting there
    not running the session manager, and start the session manager from an
    8300 running ultrix sitting somewhere else? 
    
    				thanks -- dd

445.14Translation requestedFLUME::dikeMon May 08 1989 21:529
Maybe you can explain in English what it is you are looking for.  I
checked back a half-dozen replies in this topic and didn't see
anything that I understood.

You can't run the session manager remotely because it tries to
issue ChangeHost requests, which fail when done remotely.  This is
a bug.
				Jeff

445.15answered, thanksMINNIE::DOUGto bless and not to curseWed May 10 1989 10:0513
>    You can't run the session manager remotely because it tries to
>issue ChangeHost requests, which fail when done remotely.  This is
>a bug.
    
    this answers my question, thank you.  
    
    perhaps you can suggest a course for me to take to gain as fine a
    command of english as you so obviously have. 
    
    						--dd