home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky vmsnet.sysmgt:345 comp.os.vms:18028
- Path: sparky!uunet!stanford.edu!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!wupost!usc!news.service.uci.edu!beckman.com!dsroberts
- From: dsroberts@beckman.com
- Newsgroups: vmsnet.sysmgt,comp.os.vms
- Subject: Error accessing SYSUAF file
- Message-ID: <1992Nov16.115823.1041@beckman.com>
- Date: 16 Nov 92 11:58:23 PDT
- Organization: Beckman Instruments
- Lines: 34
-
- We decided to radically change our approach to system startup for our cluster.
- It takes a very long time and the way we were doing it is very confusing. So
- we designed a table driven startup, and tried it Sunday. Everything seemed to
- work okay, except for one glitch. Login attempts get the error:
-
- "Error accessing system authorization file"
- "Error in device name or inappropriate device type for operation"
-
- Okay, sez I, the logical SYSUAF isn't defined properly. So, $ SHOW LOGICAL
- /FULL SYSUAF:
-
- "SYSUAF" = "BII$SYSTEM:SYSUAF.DAT"
-
- Hmm. exactly the same as the old startup. How about BII$SYSTEM?
-
- "BII$SYSTEM" = "$1$DUA1:[BII.SYS]"
-
- Also the same. Well, does the file exist?
-
- $ directory sysuaf
- Directory $1$DUA1:[BII.SYS]
- SYSUAF.DAT;3
- Total of 1 file.
-
- Yep, the file exists. It is indeed the same sysuaf used on all nodes in the
- cluster. I ran out of test time, so back to the old startup, and that works
- fine. Anyone got any ideas what could cause this problem?
- --
- Don Roberts Internet: dsroberts@beckman.com
- Beckman Instruments, Inc. Phone: 714/961-3029
- 2500 Harbor Bl. Mailstop X-12 FAX: 714/961-3351
- Fullerton, CA 92634 Disclaimer: Blame me, not Beckman.
- This was probably the most disastrous election result for the American
- people since James Buchanon became president. Heaven help us.
-