topic Re: stop after local profile in Operating System - HP-UX

stop after local profile

Ralf Buchhold — Fri, 22 Oct 2004 05:04:04 GMT

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

Re: stop after local profile

Simon Hargrave — Fri, 22 Oct 2004 05:21:28 GMT

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.

Re: stop after local profile

Alberto Velez — Fri, 22 Oct 2004 05:24:04 GMT

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?

Re: stop after local profile

Gary S Taylor — Fri, 22 Oct 2004 05:27:03 GMT

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

something on the lines of
export PS1="#"

Re: stop after local profile

Alberto Velez — Fri, 22 Oct 2004 05:33:34 GMT

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 :-)

Re: stop after local profile

Sridhar Bhaskarla — Fri, 22 Oct 2004 05:36:28 GMT

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

Re: stop after local profile

Stuart Urquhart — Fri, 22 Oct 2004 05:44:53 GMT

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

Re: stop after local profile

Alberto Velez — Fri, 22 Oct 2004 06:00:15 GMT

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 :-)

Re: stop after local profile

Ralf Buchhold — Fri, 22 Oct 2004 06:24:12 GMT

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

Re: stop after local profile

Geoff Wild — Fri, 22 Oct 2004 07:30:39 GMT

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

Re: stop after local profile

Jan Sladky — Fri, 22 Oct 2004 08:19:59 GMT

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

Re: stop after local profile

Govind_3 — Fri, 22 Oct 2004 08:59:03 GMT

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

Re: stop after local profile

Govind_3 — Fri, 22 Oct 2004 09:00:12 GMT

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