On Wed, Aug 23, 2000 at 09:17:48PM -0500, Brent Harding wrote: > If the script makes the file, say for example > #!/bin/sh > echo enter a username to create > read $USER > echo enter user's password > read $PASSWORD > echo $USER:$PASSWORD >>/etc/requested.users > Then on the hour in cron have it mail to me the file with a subject of > requested users, or piped the file to that newusers utility that > parces mass user entries. How can this actually break and do something > I don't want? Supposing the /etc/requested.users file were owned by > the group requestusers with my friend being a member, with permissions > of 750, so outsiders can't get the file modified? If you *really* want to do it that way, Brent, I'm not going to stop you. However, I wouldn't. -- Karsten M. Self <kmself@ix.netcom.com> http://www.netcom.com/~kmself Evangelist, Opensales, Inc. http://www.opensales.org What part of "Gestalt" don't you understand? Debian GNU/Linux rocks! http://gestalt-system.sourceforge.net/ K5: http://www.kuro5hin.org GPG fingerprint: F932 8B25 5FDD 2528 D595 DC61 3847 889F 55F2 B9B0
Attachment:
pgpk7vTSMq0Tr.pgp
Description: PGP signature