home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.aix
- Path: sparky!uunet!usc!sol.ctr.columbia.edu!destroyer!gumby!yale!mintaka.lcs.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!lwvanels
- From: lwvanels@athena.mit.edu (Lucien W. Van Elsen)
- Subject: Re: problem with putuserpw subroutine
- In-Reply-To: julie@levell.austin.ibm.com's message of 28 Jul 92 16:37:37 GMT
- Message-ID: <LWVANELS.92Jul29084952@fionavar.mit.edu>
- Sender: news@athena.mit.edu (News system)
- Nntp-Posting-Host: fionavar.mit.edu
- Reply-To: lwvanels@MIT.EDU
- Organization: Massachusetts Institute of Technology
- References: <1992Jul23.225734.9999@slate.mines.colorado.edu>
- <1992Jul28.163737.29750@awdprime.austin.ibm.com>
- Date: Wed, 29 Jul 1992 12:50:00 GMT
- Lines: 18
-
- julie@levell.austin.ibm.com (Julie L. Craft) writes:
-
- > No, you need to set up the "database" to be able to
- > READ and WRITE to it. By default, if you don't call setpwdb,
- > then you get READ access.
-
- That statement isn't quite right- If the pwdb isn't currently open,
- putuserpw _will_ do the right thing and open it with read-write access; no
- call to setpwdb is necessary. The problem is that if the pwdb is open with
- read-only access (as getuserpw leaves it), putuserpw will not try to upgrade
- the access to read-write, and subsequently fail. This should either be
- fixed, or it should be documented.
-
- -Lucien
-
- ----------------------------------------------------------------------------
- Lucien Van Elsen | lwvanels@athena.mit.edu
- MIT Athena Systems Development |
-