I'm not so sure of that any longer. He is running csh and his "pwd" is aliased to a variable called $cwd. He reported, when he ran the fully qualified path of command, pwd, (/bin/pwd) it returned "/". That suggests whatever the $cwd variable is set to is causing the odd response. That is why I asked him to run "printenv cwd" - for csh that should tell what the variable is set to.

Nothing.
But if I do "echo $cwd", this shows me the current path.
So, this variable is somewhere, but not in the environment. Right ? Where can it be ?

csh is crappy and broken by design, and having a broken prompt command doesn't help, not sure if there is any interest in investigating the issue further.

Just switch to ksh, bash or whatever shell you are familiar with.

So you're NOT in csh like you said earlier? In an earlier post it was suggested you run:
/usr/xpg4/bin/sh
That would have changed you from csh to sh (bourne shell). Are you still in that same session? I had suggested you log in to a session like you did originally.

When you say "current path" do you mean the one shown by /bin/pwd or the one previously shown by pwd without the /bin in front of it?

Yes, I am running csh.
I only used sh to test if the prompt would change, then I closed that session.

Repeating tests:
I reboot the machine and open a terminal.
The prompt says it´s at "myuser" directory.
The "pwd" command (without /bin in front) also shows "/home/staff/myuser".
The "echo $cwd" command also shows "/home/staff/myuser".

I do a "ls" command to see which files are in the current directory.
So I see I´m in the root directory, not in "myuser".
When I say "current path" I mean the actual current path (shown by /bin/pwd): "/".

Ok, that seems a good advice, but I cannot switch (permanently) the shell being used.
My company has been working that way for years and they wouldn´t want to have it changed.

But at this point, it seems the main question still to be investigated is about the cwd variable, that´s not listed in the environment, and I have no idea where it comes from.

The value is coming from $cwd. Something in your environment is setting cwd to be the <weird path> you're seeing.

For csh look for "setenv cwd <value>" statements.
global setup for all csh users is defined in /etc/login.
local setup for csh users is defined in /$HOME/.csrhc and/or /$HOME/.login

For sh/ksh look for "cwd=<value>" statements.
global setup for all sh/ksh users is defined in /etc/profile.
local setup for sh/ksh users is defined in $HOME/.profile

NB: bash has additional files - this shell is most commonly used on Linux.

Any of the environment/setup files can "source" additional files and you'd have to examine those. Also they could invoke scripts that source additional files.

If you unalias pwd it should find the system pwd (/bin/pwd) instead of using $cwd.

No, see the section "Special shell variables" in the csh manpage. The shell internally sets and updates cwd. It is not, technically, part of the environment.

1 members found this post helpful.

I see that you are right. I also see that trying to change it from command line doesn't work (in csh on Linux - I don't have a Solaris system to test). After some searching I found a nice discussion about why cwd and /bin/pwd could report different things at http://www.grymoire.com/Unix/Csh.html.

That says in part:
The above however, suggests maybe it is a symbolic link he is going to on login. OP examining the home directory path seen for the user in /etc/passwd from root (/) down to check for symbolic links might be useful.

I also found some discussion of changing csh cwd via programming including some TCL stuff. It may be OP has is executing a binary in one of his environment files that is changing this.