Operating System - HP-UX
1833608 Members
3503 Online
110062 Solutions
New Discussion

Re: stop after local profile

 
Ralf Buchhold
Regular Advisor

stop after local profile

Hello
I use an remsh (xterm on a remote server)
after the local profile (/users/username/.profile) no prompt appears.
Is there another file after the local profile used ??

Thanks
Ralf
12 REPLIES 12
Simon Hargrave
Honored Contributor

Re: stop after local profile

Likely something in your .profile hanging.

Try putting "echo done" at the end of the .profile, see if it actually gets to the very end.

If it doesn't, put "set -x" at the start of the .profile to enable shell tracing. You should then be able to see how far it gets.
Alberto Velez
Advisor

Re: stop after local profile

Hi Ralf,

I have the same case. I'm with a NIS and NFS environment, with many users and machines. Some useres can log in successfully, but a few users cannot log in in a few machines. The /etc/profile, /users/username/.profile and /users/username/.kshrc are executed succesfully, but they cannot get pompt.
Is there any temporal file to be deleted? Is ksh accessing to any other files?
Gary S Taylor
Occasional Advisor

Re: stop after local profile

Check that environmental variable
PS1
is being set in the .profile

something on the lines of
export PS1="#"

Alberto Velez
Advisor

Re: stop after local profile

I've ckecked that environment variable. It is set properly. It seems that ksh is waiting for some kind of signal, an nfs response or some like that.
Any suggestion?

Thanks anyway :-)
Sridhar Bhaskarla
Honored Contributor

Re: stop after local profile

Hi Ralf,

put a 'set -x' at the start of your profile and you should be able to see where it is waiting at.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Stuart Urquhart
Frequent Advisor

Re: stop after local profile

Is your $HISTFILE set to your NFS home directory - this seems to cause curious hangs. Try setting it to /var/tmp/.hist.$LOGNAME.
Alberto Velez
Advisor

Re: stop after local profile

GREAT!!

It worked. It seemed that the .sh_history was locked by the NFS server :S.

The solution is changing the .sh_history for a local one or putting permissions to 000, so the file cannot be accessed and this step skipped.

Thanks for your help :-)
Ralf Buchhold
Regular Advisor

Re: stop after local profile

Thanks
for the answers. Really PS1 is not set.
But I cant set PS1.

And on the other side.
It is everything ok when i write
the IP Adress an hostname from the remote-computer in the server /etc/hosts.
Any idea
Thanks Ralf
Geoff Wild
Honored Contributor

Re: stop after local profile

What happens if you temporarily disable the /users/username/.profile?

IE: mv /users/username/.profile /users/username/.profile.bad

Does it work then?

On remote host - what is the shell of the user? is it the same as localhost?

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Jan Sladky
Trusted Contributor

Re: stop after local profile

hi Ralf,

PS1 you can set,e.g,. by this way:

export PS1='$LOGNAME'"@"`hostname`":"'$PWD'"#

for all variables have a look on man of your shell

br Jan
GSM, Intelligent Networks, UNIX
Govind_3
Regular Advisor

Re: stop after local profile

It seems more like a automount issue, after login you are trying to mount some directory and the NFS server is not responding for thsi client, probably some kind of home diretcory or some kind of application being mounted. you can see that in your syslog.

Goodluck,
Govind
Govind_3
Regular Advisor

Re: stop after local profile

Let me ask you one question, Do you see the same behaviour when you try to login locally?
-Govind