01-24-2018
Xterm display immediatly dies in hpux 11.23
After install of the Sept. 2010 patch set on my hpux 11.23 system, my xterm when launched, dies immediately on the client with the xserver, with a core.xterm file in root of the hpux server. This had been working before the patch install.
I tried to find xterm patches from ITRC (yes the old name), but none of those seemed to remedy the problem. I have a second 11.23 system exhibiting the same issue with the same patch bundle applied.
The xstart program that launches the xterm, is functional and operates without issue on other HPUX server versions (11.11, 11.0, 11.31, 10.2).
Yes my display is set. The x window does appear on my client, just briefly, too rapidly to see any thing in the window. The client diagnostics do not show any trouble with the startup execution.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I go to a different terminal ctrl-alt f2
i want to be able to open up another xterm there.
How do i do it?
Specificly, I want to be able to log into another computer in term f2. I then want to open a gui term and then execute programs on one computer but have them display on mine?
I... (1 Reply)
Discussion started by: macdonto
1 Replies
2. Solaris
Say I have a daemon that dies for an unknown reason. Is there a way to track its process ID to try to determine when it dies and what causes it to go away? (2 Replies)
Discussion started by: Silver11
2 Replies
3. SCO
We have just installed a sco 600 server. Xdmcp comes up in the chooser but if you don't log in within a few minutes it disappears and you have to log in
and then out on the console before you can see it in the chooser. Xdmcp is
suppossed to be setup for continuous logins automatically. We... (0 Replies)
Discussion started by: khafner
0 Replies
4. UNIX for Dummies Questions & Answers
I am using this command but when I launch it, the font that comes up on the remote machine is very small. Is there a way to enlarge the font using some switch?
xterm -display remotemachine:0.0 & (5 Replies)
Discussion started by: zapper222
5 Replies
5. UNIX for Dummies Questions & Answers
Setup:
Two users, each likely on Windows PCs, using either putty or SecureCRT to connect to a remote Solaris server. The connection could be either telnet or ssh.
Wanted:
How can the output of one users xterm be directed to the other user so that you can easily allow someone to see what... (8 Replies)
Discussion started by: Vi-Curious
8 Replies
6. Shell Programming and Scripting
I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies
7. UNIX for Dummies Questions & Answers
Hello everyboby,
can someone write me all options for Xterm option -name. For example, I know that @d give me server ip... but, how to write something like
${USER}@${HOST}: ${PWD}$
on title bar ?
I use a connection line like this
@(XTerm, method=stdappdb) -fn 6x13 -bg AliceBlue -fg blue... (2 Replies)
Discussion started by: gogol_bordello
2 Replies
8. UNIX for Advanced & Expert Users
When ssh'ing into certain Unix boxes I'm seeing two errors that appear immediately after entering the password I've never seen. After the error message is displayed the connection closes immediately. The first is “/bin/ksh: Not owner” after which the connection is closed. And, “Read from remote... (2 Replies)
Discussion started by: twk
2 Replies
9. HP-UX
I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email.
original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies
10. UNIX for Advanced & Expert Users
I am running eod8 to connect to a linux machine running
carnesr==>uname -a
Linux hostname 2.6.32-220.2.1.el6.x86_64 #1 SMP Tue Dec 13 16:21:34 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
I have a script that opens up several xterms as follows:
/usr/bin/xterm -geometry 150x60+0-0 -name... (1 Reply)
Discussion started by: rcarnesiii
1 Replies
LEARN ABOUT HPUX
bootconf
bootconf(4) Kernel Interfaces Manual bootconf(4)
NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)