Is there some way for a Telnet session to discover where the Telnet client is?
That is, can I do something that would enable me to check for a remote
connection in my .profile, examine the address of the client system, and
conditionally set the value of e.g. PRINTER based on that location? I
sometimes have to Telnet from (ugh!) Win95 systems and would like to be able to
automagically route my printing to a nearby device.
If I have to e.g. hack login myself, would anyone care to suggest a name for a
remote-host name/address environment variable that either is fairly standard,
or stands a good chance of becoming standard if I argue loud and long enough?
The rats won the first heat, but I'm not*ed yet!