Pipe character & broken pipe error message

[Nial Gunn]

I have just installed HP-UX11i. I have copied over my .profile from my old 10.20 box which worked fine. I have uncommented the last line in the .dtprofile to ensure that the .profile is read. In the .profile I have made customisations but none relating to $TERM.

If I run echo $TERM, it is set to dtterm

If I try to type the | character, the following appears on the screen ^??

When I try to install some software that has a | character in the installation script, it errors at that line and gives me an error message about a broken pipe.

I think the 2 things are probably linked.

Please help????

[Roger Baptiste]

Hi,

Is the problem with only one userid or
with other user id's too? If it works
for root or other user id, copy the
.profile of that id and check. This is
obviously related to STTY setting in the
profile or the lack of it.

Also, try copying the
/etc/skel/.profile to your home directory
and check.

Also , see whether | is listed in stty -a output.

-raj

[harry d brown jr]

It appears you have the wrong language installed/referenced:

http://grid.let.rug.nl/~galiard/latin1.html

live free or die
harry

[Nial Gunn]

The problem occurs for both my root user and the only other user that I have created which leads me to think that the .profile isn't the problem. I also tried replacing the .profile with the original from the skel directory and that didn't change anything.

Other symptoms that I have since experienced are that if I rlogin to another HP-UX box from the problematic one, the problem exists when I try to use the pipe character on the other box. If I telnet into the problem box from a PC, the pipe character works fine.

One thing I forgot to mention earlier is that I replaced the .dtprofile on my 11i box with a .dtprofile from a HP-UX 10.20 box. Are the .dtprofile's different on the 2 different versions and could this be the problem?

If I run stty -a there is no mention of | whatsoever. Is this what you would expect to see?

With regards to the language, I am running en_GB.iso88591 according to the echo $LANG command.

If I run

LANG=en_GB.iso88591; export LANG

the variable changes but the problem with the character is still the same.

[harry d brown jr]

Check KBD_LANG ::

http://www.cs.rit.edu/~hpb/Man/_Man_Dt_html/html5/dtenvvar.5.html

http://www.cs.rit.edu/~hpb/Man/_Man_Dt_html/html1/dtlogin.1.html


live free or die
harry

[Nial Gunn]

If I run

echo $KBD_LANG

nothing is set.

I tried running

KBD_LANG=en_GB.iso88591; export KBD_LANG

That didn't solve the problem

I also tried inserting that line into the .profile and logging in again which still didn't fix the problem.

[Frank Slootweg]

If this is a 'built-in' graphics display, i.e. using the ITE (Internal Terminal Emulator), then probably /etc/kbdlang is set incorrectly.

The correct setting depends on which 'language' keyboard you have, i.e. UK English versus US English vs .... See the itemap(1M_ manual page for details. If you know the right setting, then you can probably fix it with "itemap -i -L -w /etc/kbdlang".

In any case, if this is indeed the ITE, then *first* try getting it to work *without* CDE, i.e. with a 'no-windows' (or similar) character mode login. When that works, try the same with CDE.

When/if you respond again, please post the product/part number of the keyboard (on the bottom).

[Nial Gunn]

The /etc/kbdlang says that it it set to UK English (Menu option 24.)
I tried changing it to US English using the command you suggested and the situation remained the same. I then changed it back to UK English using the same command and the problem still existed. I tried taking the box down to run level 2 (i.e. no CDE running) and the | character worked fine.

My keyboard HP part no. is A4983-60413

I think the above points to something to do with the graphical environment (CDE) Any suggestions what I could try next?

[Frank Slootweg]

Yes, the ITE correctly working without CDE and assuming that A4983-60413 is indeed a UK English keyboard (I have not checked), leads to the conclusion that it is a CDE issue. Not being a CDE/GUI-man myself,I'll have to pass that one one.

[Nial Gunn]

I think the problems been solved thanks. It was simply the drop down options on the login screen, The wrong one was selected. Oops, I suppose I should have checked the obvious thing first!!!