home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.prime
- Path: sparky!uunet!ornl!rsg1.er.usgs.gov!darwin.sura.net!jvnc.net!primerd.prime.com!tiger1.prime.com!gorton
- From: gorton@s35.prime.com (Scott Gorton)
- Subject: Re: change_project
- Message-ID: <1992Nov19.124349@tiger1.prime.com>
- Sender: gorton@tiger1.prime.com (Scott Gorton)
- Organization: Prime Computer, Inc.
- References: <9211190709.AA02434@usenet.rpi.edu>
- Date: Thu, 19 Nov 1992 17:43:49 GMT
- Lines: 29
-
- In article <9211190709.AA02434@usenet.rpi.edu>, MARK@acspr1.acs.brockport.edu writes:
- > I don't know if this has been brought up before or not, but can
- > anyone tell me why the CHANGE_PROJECT command (Primos Rev. 23.3) results
- > in an "Unexpected Error" when any other user is running CONFIG_USERS
- > or EDIT_PROFILE ?
- >
- > Just wondering.
- > Mark Weiland
- > mark@acspr1.acs.brockport.edu
- >
-
- The problem is due to an improper read/write lock on the SDF database in the SAD.
- The database should be protected with an UPDaTe lock. To remedy the situation
- change the line in SYSTEM>SET_LSR_ACLS.CPL that reads:
-
- &if [exists *>sdf -file] &then rwlock sdf sys
-
- to
-
- &if [exists *>sdf -file] &then rwlock sdf updt
-
- Since this will only take effect the next time the LOGIN_SERVER is started you
- can also manually setup the rwlock on the SDF (via: RWLOCK SAD>SDF UPDT) if
- you don't feel like stopping and restarting the LOGIN_SERVER.
-
- This will be fixed in 23.4 and appropriate rapids.
-
- Scott
-
-