Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!seismo!elsie!ado
From: ado@elsie.UUCP (Arthur David Olson)
Newsgroups: comp.unix.questions
Subject: Re: Why does vipw *require* /bin/csh ?
Message-ID: <7464@elsie.UUCP>
Date: Mon, 10-Aug-87 21:09:03 EDT
Article-I.D.: elsie.7464
Posted: Mon Aug 10 21:09:03 1987
Date-Received: Wed, 12-Aug-87 01:41:36 EDT
References: <2647@lifia.UUCP> <13848@topaz.rutgers.edu>
Organization: NIH-LEC, Bethesda, MD
Lines: 38
Keywords: vipw
Summary: back in your court

In article <13848@topaz.rutgers.edu>, ron@topaz.rutgers.edu (Ron Natalie) notes:

> . . .it prevents you from setting the ROOT default log in shell to
> something other than /bin/sh or /bin/csh.  You should
> avoid doing that anyway.  It's usually best to use a working shell
> for root (like a System V Bourne shell) rather than any of the buggy
> shells that come with Berkeley UNIX.

We tried to follow your advice here at Elsie, Ron. . .but vipw wouldn't
accept "/bin/ksh" after we'd obtained it from those wonderful folks who
brought you System V.

The change that's been applied to "vipw.c" here:

	*** 3.1/vipw.c	Mon Aug 10 21:06:57 1987
	--- 3.2/vipw.c	Mon Aug 10 21:06:58 1987
	***************
	*** 129,138 ****
	--- 136,152 ----
				if (strncmp(++cp, "/:", 2))
					break;
				cp += 2;
	+ #ifdef ASWAS
				if (*cp && strcmp(cp, "/bin/sh") &&
				    strcmp(cp, "/bin/csh"))
					break;
				ok++;
	+ #else /* !ASWAS */
	+ 			if (*cp == '\0' ||
	+ 				(*cp == '/' && access(cp, X_OK) == 0))
	+ 					++ok;
	+ 			break;
	+ #endif /* !ASWAS */
			}
			fclose(ft);
			if (ok) {
-- 
UUCP: elsie!ado		Elsie and Ado are trademarks of Borden, Inc. and Ampex.