topic Re: export command is not working in Operating System - HP-UX

export command is not working

Yarok — Thu, 02 Jun 2011 11:31:51 GMT

Hello,

On HP-UX b.11.11 (C-8000), I try to run export command i.e export TERM=vt100.

Please advice,

Yaron

Re: export command is not working

Duncan Edmonstone — Thu, 02 Jun 2011 11:39:42 GMT

so whats not working then?

if you set a TERM environment variable as you showed, it just sets it in the current shells environment - it won't actually change anything - what are you expecting to happen? Maybe change the settings for the terminal? If so you should run the "tset" command after setting the environment variable...

export TERM=vt100
tset

HTH

Duncan

Re: export command is not working

點燃 — Thu, 02 Jun 2011 11:46:11 GMT

The export command should be working 11.11. Please post the error message here

Re: export command is not working

Yarok — Thu, 02 Jun 2011 11:48:50 GMT

even if I try: man export it says " no manual entry for export "

Re: export command is not working

Yarok — Thu, 02 Jun 2011 11:51:29 GMT

error message:

export: Command not found

Re: export command is not working

Duncan Edmonstone — Thu, 02 Jun 2011 12:02:33 GMT

export is not actually a command, it is a shell built-in for the sh and ksh shells...

I gues you are using another shell such as csh or tcsh which doesn't have export... why you would want to use these terrible shells I don't know, but the equivalent to "export TERM=vt100" in csh would be "setenv TERM vt100"

HTH

Duncan

Re: export command is not working

Dennis Handly — Fri, 03 Jun 2011 17:20:27 GMT

>even if I try: man export it says "no manual entry for export"

As Duncan said, try "man ksh" or "man sh-posix" and look for "export".

Re: export command is not working

Yarok — Sun, 05 Jun 2011 10:43:21 GMT

Usually, I uses tcsh or sh shells.

1. How can I know what shell Im running with (I mean, is there any command that displays the shell)?

2. what are the benefits of ksh over others tcsh or sh in my case?

BR,

Yaron

Re: export command is not working

Dennis Handly — Tue, 02 Aug 2011 14:15:15 GMT

>Usually, I use tcsh or sh shells.

export works in sh/ksh, bash, etc

>1. How can I know what shell I'm running?

Typically you would just know. :-)
You can "echo $SHELL" but that's your login shell and can be changed.
I've found that if you try to execute a bogus command, the name of the shell is mentioned.
http://h30499.www3.hp.com/t5/Languages-and-Scripting/shell/m-p/4754063#M29768

>2. what are the benefits of ksh over others tcsh or sh in my case?

There is something terribly wrong if you mention tcsh and sh together, since they don't get along. :-)
http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/
http://h30499.www3.hp.com/t5/Languages-and-Scripting/Which-Shell-is-best/m-p/4783404#M30508
http://h30499.www3.hp.com/t5/Languages-and-Scripting/KSH-to-CSH-conversion-not-working/m-p/5274603#M41617

Basically sh/ksh are nearly identical and are real shell.
tcsh is derived from the scummy C shell.

Re: export command is not working

Yarok — Mon, 06 Jun 2011 06:49:11 GMT

Many thanks, I followed the links and informed myself (some with mine old thread :))

BTW, I probably type tcsh to get a comfortable env, so I couldn't run export.

BR,

Yaron

Re: export command is not working

Steven Schweda — Wed, 15 Jun 2011 21:11:00 GMT

> 1. How can I know what shell Im running
> with (I mean, is there any command that
> displays the shell)?

I had intended to suggest this a while ago,
but got distracted.

echo $0

dy # echo $0
bash
dy # /bin/sh
dy # echo $0
/bin/sh
dy # sh
dy # echo $0
sh

Apparently not good in every case, though:

dy # /bin/csh
# echo $0
No file for $0.