Re: AIX $SHELL variable and Fourgen Screens
Posted in 1994
In Article <3cq6qm$ern@mother.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. > >However, after the user signs-on here, a second 4gen screen is called using >the RUN command. Well...this doesn't work. What happens is the initial >screen blanks out for a second, then repaints itself--bringing the user >back to where they were initially. > What I'd do is leave there user login running a shell. In the .profile or .login (shell dependant) for that login, set any environment variables you like and as the last line in the file, use the line exec progname [args] where, obviously, progname is the program you want to run. This will cause the SHELL environment to be correct for subsequent RUN commands, but the login shell is replaced by the invocation of the program. When they quit that program, a new getty will be spawned on the terminal. The only way they'll then accidentally be able to get at the shell is by the use of ctrl-c whilst your .profile is executing. You can trap for this, but this has been known to cause problems with the correct use of ctrl-c under Informix so you may just want to take the chance that they won't use it. Regards Neil