On Tue, 2002-11-19 at 20:31, David Guntner wrote: > Well, the TERM value that *I'm* using doesn't come in to play, in this > case. :-) I'm using a PHP web application which uses expect to spawn > screen and do its thing. So it's the apache user that's executing this > command from within the web server. There's no TERM set for that, nor > should there be (as far as I know). Is there a setting/command-line > switch/something else that can be used to tell screen to disregard TERM (or > the lack thereof?) > --Dave > --
See if this is relevant to your situation: "On the other end, screen understands one set of control codes. It relies on the application using these codes. This means applications that run under screen must be able to adapt their control codes to screen. The application should use the TERM variable and termcap or terminfo library to find out how to drive its terminal. When running under screen, the terminal is virtual and is only defined by the set of control codes that screen understands. The TERM variable is automatically set to "screen" and the "screen"-entries should exist in the databases. If your application uses hardcoded control codes rather than a database, you are on your own. Hint: The codes understood by screen are a superset of the very common definition named "vt100"." This was from /usr/share/doc/screen-3.9.10/FAQ. It seems to me that a good place to start looking is at the environment variables present for apache. HTH, LX -- ��������������������������������������������������� Kernel 2.4.18-6mdk Mandrake Linux 8.2 Enlightenment 0.16.5-11mdk Evolution 1.0.2-5mdk Registered Linux User #268899 http://counter.li.org/ ���������������������������������������������������
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
