Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!wb3ffv!ka3ovk!raysnec!shwake
From: shwake@raysnec.UUCP (Ray Shwake)
Newsgroups: comp.unix.xenix.sco
Subject: Re: Problems with guest login script
Message-ID: <103@raysnec.UUCP>
Date: 16 Oct 90 20:56:15 GMT
References: <83@abode.UUCP> <27167978.1F9E@marob.masa.com>
Organization: IRS/CI - Technical Solutions Branch
Lines: 16

>In article <83@abode.UUCP> jtb@abode.wciu.edu (John P. Gibbons) writes:
>> [ about getting the shell to exit after executing stuff in .profile ]

	[ Can't access .edu sites, thus the following posting. ]

Perhaps I'm missing something in John's original inquiry. Why not simply
run a shell script AS the shell, that shell script containing those
assignments and operations that would have gone into the .profile.

For more than a year I've been running a dialup demo for "guest" logins,
the password entry for which reads something like:

	guest:*:204:99:guest login:/usr/demo:/usr/demo/guest.sh

Through proper use of traps, SHELL assignments and other tricks, I've 
kept everyone out of an interactive shell.