Date: Fri, 23 Jul 2010 15:46:31 -0400 From: Jim Trigg <jtrigg@spamcop.net> To: freebsd-ports-mailinglist <freebsd-ports@freebsd.org> Subject: Re: Problems with sysutils/screen (GNU Screen) Message-ID: <AANLkTin7%2BgVdpkx9ZdQ-y4hFN9vOXdK4v7J-DhjhGDk4@mail.gmail.com> In-Reply-To: <4AF2FCF6EE2B406F9B60E87D63C7F1F0@sunrise> References: <AANLkTinUH0ALwZVi-UZ0BUdQZV=RMXfW5FMePuneMGHp@mail.gmail.com> <4AF2FCF6EE2B406F9B60E87D63C7F1F0@sunrise>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 23, 2010 at 3:42 PM, Scott Sanbeg <ssanbeg@gmail.com> wrote:
> /etc/termcap is symlinked to /usr/share/misc/termcap, which if not available
> during your session (singer-user mode, for instance), produces that exact
> type of error message. Test if the termcap db is actually available.
It is; further, I will observe that unsetting the TERMCAP environment
variable makes it work in an interactive shell window, but when I use
the "screen {command}" functionality it fails (and I can't get logging
to work to find out what error I'm actually getting; the window closes
too fast for me to see the error).
Thanks,
Jim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTin7%2BgVdpkx9ZdQ-y4hFN9vOXdK4v7J-DhjhGDk4>