On 6/4/2012 9:55 AM, Chet Ramey wrote:
That's not exactly it, but the idea is right. isnetconn() (previously issock()) has been around since bash-1.13. If I had to guess, I'd say late August 1992 or 1993. It wasn't inherited from csh. The original requests were along the lines of having something to set the remote environment when running rsh or rcp. As you can see, this long predates ssh. As ssh became more popular, there were different ways to accomplish the same thing (e.g., put BASH_ENV=startup-file into ~/.ssh/environment), but there were still requests to leave the feature in bash. It's still there today.
I guess I'm just looking for confirmation that what I'm doing is correct. I've been going to some lengths to ensure that the environment that I get for a non-interactive script gets at least the minimal environment that I expect. I do this by expecting my .bashrc to always get pulled in and to see if PS1 is set. If PS1 is *not* set then I pull in a common script that sets my environment the same as if I had set it in my .bash_profile .
Does this sound correct? -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net
