Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!mcvax!hp4nl!mhres!mh_co2!vrh
From: vrh@mh_co2.mh.nl (Michael Verheij)
Newsgroups: comp.unix.questions
Subject: Re: vipw - the program
Keywords: vipw
Message-ID: <2527@mhres.mh.nl>
Date: 28 Oct 88 11:47:01 GMT
Article-I.D.: mhres.2527
References: <218@fantasci.UUCP> <14043@mimsy.UUCP> <3182@tekcrl.CRL.TEK.COM>
Sender: news@mhres.mh.nl
Reply-To: vrh@mh_co2.mh.nl (Michael Verheij)
Organization: Multihouse N.V.
Lines: 20

In article <3182@tekcrl.CRL.TEK.COM> eirik@tekcrl.TEK.COM (Eirik Fuller) writes:
>I like these scripts to implement vipw, but I wonder, do systems
>without vipw know about /etc/ptmp?  The point of vipw as I understand
>it is that /bin/passwd knows enough not to change a password if
>something else (vipw, for instance) is in the middle of changing
>/etc/passwd.  Seems to me vipw as a script buys you something only if
>a) /bin/passwd already knows of /etc/ptmp or b) /bin/passwd is rigged
>to know of /etc/ptmp.
>

Our Multipower Series/2 (a system with National Semiconductors' GENIX V.3 OS)
has no vipw-command. But when you examine the strings found in /bin/passwd
(which you can do with the strings-command), the program definitely tests
for the existence of /etc/pmp. If you create the file /etc/ptmp and you
try to change your password afterwards, then the passwd-program prompts
you that the password can't be changed, because a "temporary file exists".
Michael Verheij (using Netnews)
USENET: vrh@mh.nl via European backbone (mcvax).
UUCP:   ..!mcvax!mhres!vrh
"Experience comes with the amount of equipment ruined."