Operating System - HP-UX
1833772 Members
2284 Online
110063 Solutions
New Discussion

opening shell/xterm window locally under HP desktop does not work

 
Matthias Oswald
Advisor

opening shell/xterm window locally under HP desktop does not work

We have still the problem that when locally logging in on certain machines, opening a shell window does not return a prompt.
The window is hanging.
exporting HISTFILE to a non NFS filesystem cured this problem when doing remsh.

The automounting works, at least when doing cd.
NFS looks also okay.
The home directory is mounted with the following options:
auto.direct:/usr/users/it -rw,timeo=9 nfsprod:/userit

Any idea ?
Thanks a lot.

Matthias.
mabios
5 REPLIES 5
Ron Cornwell
Trusted Contributor

Re: opening shell/xterm window locally under HP desktop does not work

I ran into something similar in my SNA III class. The problem there ended up being that there was a space at the end of that users line in the /etc/passwd file. I can't remember but there is a log file on the system that has more info about dtterm windows.
Ron Cornwell
Trusted Contributor

Re: opening shell/xterm window locally under HP desktop does not work

The error file I was thinking of is $HOME/.dt/errorlog.
S.K. Chan
Honored Contributor

Re: opening shell/xterm window locally under HP desktop does not work

NFS file locking problem maybe ..?
Can you try this .. (on both the client and server)
# ps -ef|grep rpc.lockd
# kill -9
# ps -ef|grep rpc.statd
# kill -9
# cd /var/statmon
# rm -R sm.bak
# rm -R state.bak
# mv sm sm.bak
# mv state state.bak
# /usr/sbin/rpc.statd
# /usr/sbin/rpc.lockd
Robin Wakefield
Honored Contributor

Re: opening shell/xterm window locally under HP desktop does not work

Hi Matthias,

Have you tried putting "set -x" at the top of your .profile ?

One other possibility is unix mail, if you've got a non-standard /var/mail setup.

Rgds, Robin.
Alex Glennie
Honored Contributor

Re: opening shell/xterm window locally under HP desktop does not work

Try editting /etc/rc.config.d/nfsconf:
LOCKD_OPTIONS="-p 4045"

any joy ?