Sponsored Content
Operating Systems HP-UX Verify 4 GB Limit is overcome in 64 Bit Processor Post 302789889 by allanbm on Thursday 4th of April 2013 11:42:33 AM
Old 04-04-2013
Quote:
Originally Posted by Corona688
Verify that you're running 64-bit executables and not 32-bit executables and you've verified that you have a 64-bit address space.
Hi Corona688,

Thanks for responding.
Yes I am executing 64 bit executable.
But how do I verify that I am using a 64-but address space?
Is there a some script or a system command that can tell me this?
PS:- I am on a HP-UX Itanium machine

Cheers,

-Allan
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Solaris (verify 64 or 32 bit

Hello !! Does anyone know how can I verify if my Solaris is 32 or 64 bit ?? Thank you ! Witt (3 Replies)
Discussion started by: witt
3 Replies

2. Shell Programming and Scripting

How to overcome Segmentation Fault in Unix ??

Hi.. I want to add a line of data to a already existing file.. When i use echo "1i\nGROUP_NAME,JOB_NAME,STATUS,PROCESS_GROUP,JOB_START,JOB_END \n.\nwq" | ex -s abc.txt where abc.txt contains only Hello Testing Insert I am getting this.. dumb: Unknown terminal type ksh: 19464... (4 Replies)
Discussion started by: charan81
4 Replies

3. AIX

LPAR processor/virtual processor settings

Question is on setting of Physical and Virtual processors for LPARs to make proper use of virtualization capabilities. Environment is a 8-way p570 with 4 LPARs. lparVIO1 and lparVIO2: AIX 5300-04-01 Mode/Type= Shared-SMT/Capped Minimum Processors= 0.10 Desired Processors= 0.50 Maximum... (1 Reply)
Discussion started by: guttew
1 Replies

4. Linux

Built in ram limit for 64 bit

Hey all, I have been thinking about getting a new computer, and the motherboard I am looking at is capable of holding up to 8 Gb of ram. Now it appears as though for 32 bit linux, in order to use more than 4 Gb of ram, you had to enable a certain option in the kernel, but if I remember... (2 Replies)
Discussion started by: kermit
2 Replies

5. Solaris

how to know the processor bit capacity

how to know for a particular solaris machine whether i am having a 64 bit or 32 bit processor??? like for machine with details SunOS 5.8 Generic_108528-20 sun4u sparc SUNW,Sun-Blade-100 (3 Replies)
Discussion started by: mobydick
3 Replies

6. Programming

a large file causes segment, how to overcome?

When printing a large file, segment occured. but part of it can be printed normally. There seems no mistake in usage. How to solve the problem. Actually, the file is not very very large. Only 300-400 A4 pages. Thanks (1 Reply)
Discussion started by: cdbug
1 Replies

7. HP-UX

[Solved] processor type and bit information

Hi, I'm trying to download a compatible Oracle Client software for a HP-UX machine. I'd like to know if ... 1) HP-UX is 32 bit or 64 bit? 2) Processor type - Itanium or regular? when I execute uname -a I get HP-UX B.11.11 U 9000/800 728684161 unlimited-user license Based on the... (7 Replies)
Discussion started by: luft
7 Replies

8. Shell Programming and Scripting

overcome unwanted input values in korn shell

Hi All, we are doing automation for installation of oracle, a) ORACLE_HOME_NAME b) ORACLE_HOME above are the argument we need to pass during the script execution, while doing this someone issue the value like ORACLE_HOME=/optware/oracle/11g;rm -rf /optware/oracle/10g its removing... (1 Reply)
Discussion started by: kamauv234
1 Replies
pa_maxssiz(5)							File Formats Manual						     pa_maxssiz(5)

NAME
pa_maxssiz: pa_maxssiz_32bit, pa_maxssiz_64bit - maximum size (in bytes) of the stack for a user process running under the PA-RISC emulator on an Integrity system VALUES
Default Allowed values DESCRIPTION
User programs on HP-UX systems are composed of five discrete segments of virtual memory: text (or code), data, stack, shared, and I/O. PA-RISC binaries running under Itanium-based system using the PA-RISC emulator have their stack segment size (which includes both the mem- ory stack and the RSE stack) determined by or The emulated stack from the process perspective is the same as the stack if the process were executed on a PA-RISC machine without the emu- lator. The actual (non-emulated) process stack (both memory and RSE) for an emulated process are of a non-configurable size and are used solely for the internal use of the emulator for a PA-RISC process on Itanium-based system. This tunable therefore represents the required value of or on a corresponding PA-RISC machine to execute the emulated process plus working space for the emulator itself. As with the stack address space sized by the address space used by the emulator is both private to the process and not usable for other purposes regardless of whether the emulator stack grows to encompass the full range or not. As a consequence, the tunable value may be viewed as an amount of process data address space which will be unavailable to this PA-RISC process. Caution is advised especially for 32 bit processes since the default address space model only provides 1 Gb of private data space. Setting this tunable too high will result in execution failure when other allocations (private calls or calls) fail due to insufficient available address space. If this occurs, revise the address space model of the failing PA-RISC executable using to allow more private data virtual address space or lower the tunable. Who is Expected to Change This Tunable? Anyone. Restrictions on Changing Given that the user memory stack size is not modifiable by this tunable, it is expected that detailed knowledge of the PA-RISC emulator memory usage is needed before modifying this tunable. When Should the Value of This Tunable Be Raised? This tunable should be raised if the PA-RISC emulator on Itanium-based system requires additional space for stack emulation. What Are the Side Effects of Raising the Value? The PA-RISC emulator will use more of the virtual address space for stack, leaving less virtual address space for data allocations. Rais- ing the value too high will result in application failure when data allocations fail due to insufficient virtual address space. Since it may not be known which processes are based off of PA-RISC binaries and which off Itanium-based binaries, arbitrary raising of this tunable is discouraged. When Should the Value of This Tunable Be Lowered? This tunable should only be lowered if the workload for the PA-RISC emulator is known on the system, more space than is needed is currently used for stack emulation, and swap space (either reserved or allocated) is at a premium on the system. What Are the Side Effects of Lowering the Value? Lowering this tunable will decrease the available stack space for emulated PA-RISC binary executions. Emulated processes needing larger stacks will fail stack growth requests (just as lowering or may cause process termination due to failure to grow stack). What Other Tunable Values Should Be Changed at the Same Time? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
chatr(1), mmap(2), sbrk(2), maxssiz(5). Integrity Systems Only Tunable Kernel Parameters pa_maxssiz(5)
All times are GMT -4. The time now is 05:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy