cottrell@nbs-vms.ARPA (02/26/85)
/* > > Or put a test in the .profile > > > > if [ `tty` = "/dev/tty??" ] > > then > > TERM=5620 # or whatever > > fi > > Doesn't do a damn thing if your password file entry reads: > > jblow:ABCDEFGHIJKL.:69:1:Joe Blow:/usr/jblow:/foo/bar/application > > and "/foo/bar/application" happens to be some screen-oriented application > that doesn't want to know how to parse a shell script. > > Oh yes, you can't set TZ for the benefit of the application, either, for > the same reason... > > (Most users at our customer sites have exactly such an application as > their login shell.) > > Guy Harris > {seismo,ihnp4,allegra}!rlgvax!guy Oh JHFC Guy, RTFM :-). Those users could have their .profile do all that stuff, then `exec' their program as the last statement. If your users are on the novice side, I'm sure some Guy at your site could set it up for them :-). jim */
guy@rlgvax.UUCP (Guy Harris) (02/26/85)
> Those users could have their .profile <set TERM and TZ>, then `exec' their > <login shell> as the last statement. That can be done - it's what we did before we fixed "login" to permit you to set TERM and TZ directly. However: 1) it's a kludge, the need for which can be obviated by a minor change to "login"; 2) it requires the system administrator to go through a song-and-dance to set up their account ("No, Fred, you don't just set their "shell" field to "/op/op/programs/shell", you leave it blank and stick the following in their .profile...") - i.e., it renders the "shell" field of the password file largely useless. Guy Harris {seismo,ihnp4,allegra}!rlgvax!guy