wderouch@blackbird.afit.af.mil (William J. DeRouchey) (08/03/90)
I have tcsh as my default shell at login and now when I execute the script command in a wsh window at the console I get the following: Warning: no access to tty; thus no job control in this shell... exit The script exits and I have no way of using script. If I invoke the csh from within a wsh running tcsh I get the same results. Thanks in advance for any assistance.
olson@anchor.esd.sgi.com (Dave Olson) (08/04/90)
In <1669@blackbird.afit.af.mil> wderouch@blackbird.afit.af.mil (William J. DeRouchey) writes: | I have tcsh as my default shell at login and now when I execute the | script command in a wsh window at the console I get the following: | Warning: no access to tty; thus no job control in this shell... | exit | | The script exits and I have no way of using script. If I invoke the | csh from within a wsh running tcsh I get the same results. | | Thanks in advance for any assistance. This sounds like you are running 3.2, which still had the pipe based script. 3.3 has the 4.3BSD script which uses pty's, so you should have no problem once you upgrade to 3.3. I believe the man page for script in 3.2 and earlier had a note that programs that 'needed' to do tty ioctls would not work under script. Many screen editors (and programs like ksh and tcsh) fall into this category. -- Dave Olson Life would be so much easier if we could just look at the source code.