Xref: utzoo comp.unix.questions:9375 comp.bugs.sys5:570
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!lll-tis!oodis01!uplherc!sp7040!marvin!jsp
From: jsp@marvin.UUCP (Johnnie Peters)
Newsgroups: comp.unix.questions,comp.bugs.sys5
Subject: Re: SVR3 passwd changes mode of passwd file
Summary: This is for your protection
Message-ID: <7@marvin.UUCP>
Date: 23 Sep 88 00:32:08 GMT
References: <3394@dunkshot.mips.COM>
Lines: 30

In article <3394@dunkshot.mips.COM>, dce@mips.COM (David Elliott) writes:
> 
> It turns out that the System V (or at least SVR3) version of the
> passwd command will cause the resultant passwd file to be mode
> 0444.  I have had a couple of complaints about this, and would like
> to decide on a solution.
> 
> Is it reasonable to have passwd fix the mode of the new /etc/passwd
> to be the same as the current /etc/passwd?

	It is entirely reasonable for passwd to set the modes of /etc/passwd
to 0444.  I fyou don't believe this try working for a company like Unisys
in O.S. support for unix.  The first time a customer calls and says things
like:

	I just accidentaly deleted my passwd file.  What can I do?

	I saved the passwd file and now it wont let anybody on.  What
	do I do?

	I forgot the root password.  What do I do?

you will understand why the passwd file is protected as well as possible.

	What you say,  "That can never happen to me!!!!!  I know what I
am doing!!!!!!!"  Well I know what I am doing and a few days ago spent
an hour restoring miscelaneous files because of a "MINOR" mistake.  You
will too one day.

					--  Johnnie  --