>Number:         9162
>Category:       pkg
>Synopsis:       ssh man-page teases about /etc/environment
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager (NetBSD software packages system bug manager)
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 10 08:57:01 2000
>Last-Modified:
>Originator:     Richard Rauch
>Organization:
  "I probably don't know what I'm talking about."  --rkr@rkr.kcnet.com
>Release:        NetBSD/i386 1.4.1
>Environment:
	
System: NetBSD rkr.kcnet.com 1.4.1 NetBSD 1.4.1 (olibGENERIC) #3: Tue Nov 30 01:09:25 CST 1999 root@rkr.kcnet.com:/usr/src/sys/arch/i386/compile/olibGENERIC i386


>Description:
  Notably for window(1), I would like to have ssh forward my TERMCAP variable
  so that the TERM setting can be honored by remote sites.  (window sets
  up a custom TERMCAP variable when it starts, and a funky TERM name.
  The remote is unlikely to support the named TERM, and window's TERMCAP
  is not at all vt100 compatible, so you are in a mildly sticky spot.)
  (Some of this overlaps with ssh and window PR's, but it's really a distinct
  problem.)

  Anyway.  The ssh man-page mentions /etc/environment can be used to tailor
  the environment variables that one forwards.  If there's an example, it's
  not pointed out.  And the man page really isn't detailed enough to give
  a useful answer.  (I had HOPED that a line reading ``TERMCAP=$TERMCAP''
  would suffice.  It does not.)

  An example file might help.  Or a little bit of elaboration in
  the man-page.  If an example exists, then either I somehow missed it,
  or it's not referenced in the man-page.
>How-To-Repeat:
  Try to use ssh from within a window (or even a screen, really, though
  screen emulates vt100 fairly well).
  Discover that TERM-related environment variables aren't being exported.
  Try to figure out how to get ssh to do it for you.
  Puzzle.
>Fix:
  None offered.

  You can move the environment variables by hand of course.  But you
  shouldn't normally have to do that.  Someone who has already figured
  out what /etc/environment is supposed to look like, or who is willing
  to traipse around the patented/export-controlled stuff, might offer
  an example, or documentation on the /etc/environment file.
>Audit-Trail:
>Unformatted: