Date: Tue, 9 May 1995 03:20:32 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: wsantee@wsantee (Wes Santee) Cc: freebsd-ports@FreeBSD.org Subject: Re: pdksh choading on exec command Message-ID: <199505091020.DAA00515@gndrsh.aac.dev.com> In-Reply-To: <199505090707.AAA00228@wsantee> from "Wes Santee" at May 9, 95 00:07:50 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > 'Lo all. > > I'm using the -current kernel sup'ed about and hour ago and just > compiled the port of pdksh (also supped about an hour ago). After all > was said and done and I set up an account with pdksh as default shell, > I noticed that whenever I executed a command that tried to clear the > screen, I would get: > > /<path>/<to>/<command>:21: bad substitution > > Looking at /usr/bin/clear I see it is just doing this: > > exec tput clear > > Typing this in at the pdksh prompt, it logged me out of the system. > This is all using terminal type cons25. I haven't yet tried with > vt100, et al. Just entering 'tput clear' worked fine. Has anybody > else dealt with this before I go and try to make sense of exec.c in > the pdksh distribution? Are you clear on what ``exec'' does?? It replaces the running tcsh by a copy of ``tput''. When tput exits you are logged out since you no longer have a shell. What happens if you type /usr/bin/clear? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505091020.DAA00515>