Re: AIX $SHELL variable and Fourgen Screens
Posted in 1994
In article <3cq6qm$ern@mother.usf.edu>, smorrow@dotrisc.cfr.usf.edu (Steve Morrow) writes: >Our solution was just to assign the program name to the $SHELL variable >(ie, make the program the login shell). This works fine when the first >screen is called (which is an "application log-in" screen). The user signs >on and boom--they're there. Steve, I would attempt putting the program into the /etc/passwd entry for a shell the user runs at login time instead of messing with $SHELL. I haven't tried this so you're on your own. It should be attempted, and if you can't use the program, then put a shell-script in that calls the program. Put a couple of exit statements at the end of the shell-script to add a little more security. The other thing you SHOULD do with the RUN command is to put an exec at the beginning of the command and eliminate a shell being created: Example: Typical run statement: RUN "program.4ge arg1 arg2" Add the exec: RUN "exec program.4ge arg1 arg2" You should TEST THIS FIRST with a simple little program that has these two run statements in a menu. Some implementations of exec will actually overlay the current shell permanently, so that when the called program is over, so is the calling program. UNIX is still un-standard, just like PC-DOS is becoming. But at least it's "open". :-) Happy Holidays! Tim Schaefer The Computer Business Co. Ft. Lauderdale, FL. inxutil@aol.com PS. If this message is word-wrapped goofy thank America On-Line...