home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #30 / NN_1992_30.iso / spool / comp / os / vms / 19448 < prev    next >
Encoding:
Internet Message Format  |  1992-12-16  |  1.5 KB
  1. Path: sparky!uunet!spool.mu.edu!agate!ucbvax!UNODE2.NSWC.NAVY.MIL!SYSTEM_JM
  2. From: SYSTEM_JM@UNODE2.NSWC.NAVY.MIL ("SYSTEM SUPPORT")
  3. Newsgroups: comp.os.vms
  4. Subject: Re: How to prevent login.com from running
  5. Message-ID: <9212170405.AA00781@ucbvax.Berkeley.EDU>
  6. Date: 16 Dec 92 17:58:00 GMT
  7. Sender: daemon@ucbvax.BERKELEY.EDU
  8. Distribution: world
  9. Organization: The Internet
  10. Lines: 28
  11.  
  12. Date sent:  16-DEC-1992 12:55:58 
  13. >> Lori Gavin writes:
  14. >>
  15. >> I was wondering if there is any way to globally not run any users's 
  16. >> login.coms.
  17. >>  
  18. >
  19. >My suggestion would be to go into AUTHORIZE and set something like the 
  20. >following:
  21. >
  22. >    UAF> MOD username/LGICMD=ASDKJFDSA
  23. >
  24. >This would solve the problem, unless of course the user has a com file such
  25. >as ASDKJFDSA.COM. The trick is to set that value to something your user(s)
  26. >would be highly unlikely to name a com file.
  27.  
  28. Or "UAF> MOD username/LGICMD=NL:".  Then you wouldn't have to worry about what 
  29. the user called his/her .COM files.
  30.  
  31. *******************************************************************************
  32. ** Jim Matthews                                                              **
  33. ** Naval Surface Warfare Center Dahlgren Division                            **
  34. ** Code N23A                                                                 **
  35. ** Dahlgren, VA 22448-5000                                                   **
  36. ** Internet: system_jm@unode2.nswc.navy.mil                                  **
  37. *******************************************************************************
  38.  
  39.  
  40.