10-22-2008
Hi mrvitas,
Please set kernel parameters for HP-UX. It is related to that max proc /threads.
Hope this help.
10 More Discussions You Might Find Interesting
1. HP-UX
We are a Lawson shop trying to upgrade our Lawson environment from an old version to a new one. When we run the install scripts on one of our systems (RP8400, HP-UX 11.i) we get a Memory Fault error and it core dumps. HP support has taken an output of TUSC and then pointed us to the application... (2 Replies)
Discussion started by: dnardi212
2 Replies
2. UNIX for Advanced & Expert Users
I am running HP-UX B.11.11.
I'm increasing a parameter for a database engine so that it uses more memory to buffer the disk drive (to speed up performance). I have over 5GB of memory not being used.
But when I try to start the DB with the increased buffer parameter I get told.
"Not... (1 Reply)
Discussion started by: cjcamaro
1 Replies
3. Programming
I need to create a shared library to access an in memory DB. The DB is not huge, but big enough to make it cumbersome to carry around in every single process using the shared library. Luckily, it is pretty static information, so I don't need to worry much about synchronizing the data between... (12 Replies)
Discussion started by: DreamWarrior
12 Replies
4. Programming
I am writing a shared library in Linux (but compatible with other UNIXes) and I want to allow multiple instances to share a piece of memory -- 1 byte is enough. What's the "best" way to do this? I want to optimize for speed and portability.
Obviously, I'll have to worry about mutual exclusion. (0 Replies)
Discussion started by: otheus
0 Replies
5. Programming
I mean, I malloc a segment of memory, maybe 1k maybe 20bytes.. assume the pointer is pMem How can I know the content pMem refered is all Zero or \0 . I know memcmp but the second parameter should another memory address... thanx (4 Replies)
Discussion started by: macroideal
4 Replies
6. UNIX for Dummies Questions & Answers
Hi all,
I have been working on shared memory. I have created the shared memory and a linked list of 5 nodes. Now I want to attach the linked list to shared memory. When we attach a shared memory it returns a void pointer, but here I am in a fix , how to relate this void pointer to linked list.... (1 Reply)
Discussion started by: jimmyuk
1 Replies
7. Programming
Hi all,
I have been working on shared memory. I have created the shared memory and a linked list of 5 nodes. Now I want to attach the linked list to shared memory. When we attach a shared memory it returns a void pointer, but here I am in a fix , how to relate this void pointer to linked list.... (4 Replies)
Discussion started by: jimmyuk
4 Replies
8. Red Hat
unable to remove shared memory using ipcrm -m in linux
$ ipcs -m
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 32768 root 644 80 2
0x00000000 65537 root ... (4 Replies)
Discussion started by: LinuxLearner
4 Replies
9. UNIX and Linux Applications
Hi, folks,
A new release, v.0.30.1, of CK-ERP, has been posted, at SourceForge.Net, sourceforge.net/projects/ck-erp .
New features comprise seven new modules (ck-teacher, ck-counsellor, ck-student, ck-applicant, ck-family, ck-registrar, ck-eduadmin) for deployment within educational... (0 Replies)
Discussion started by: chiukay
0 Replies
10. Programming
Hello.
I am new to this forum and I would like to ask for advice about low level POSIX programming.
I have to implement a POSIX compliant C shared library.
A file will have some variables and the shared library will have some functions which need those variables.
There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies
IPCS(1) BSD General Commands Manual IPCS(1)
NAME
ipcs -- report System V interprocess communication facilities status
SYNOPSIS
ipcs [-abcMmopQqSsTt]
DESCRIPTION
The ipcs utility provides information on System V interprocess communication (IPC) facilities on the system.
The options are as follows:
-a Show the maximum amount of information possible when displaying active semaphores, message queues, and shared memory segments. (This
is shorthand for specifying the -b, -c, -o, -p, and -t options.)
-b Show the maximum allowed sizes for active semaphores, message queues, and shared memory segments. The ``maximum allowed size'' is
the maximum number of bytes in a message on a message queue, the size of a shared memory segment, or the number of semaphores in a
set of semaphores.
-c Show the creator's name and group for active semaphores, message queues, and shared memory segments.
-M Display system information about shared memory.
-m Display information about active shared memory segments.
-o Show outstanding usage for active message queues, and shared memory segments. The ``outstanding usage'' is the number of messages in
a message queue, or the number of processes attached to a shared memory segment.
-p Show the process ID information for active semaphores, message queues, and shared memory segments. The ``process ID information'' is
the last process to send a message to or receive a message from a message queue, the process that created a semaphore, or the last
process to attach or detach a shared memory segment.
-Q Display system information about messages queues.
-q Display information about active message queues.
-S Display system information about semaphores.
-s Display information about active semaphores.
-T Display system information about shared memory, message queues and semaphores.
-t Show access times for active semaphores, message queues, and shared memory segments. The access times is the time of the last con-
trol operation on an IPC object, the last send or receive of a message, the last attach or detach of a shared memory segment, or the
last operation on a semaphore.
If none of the -M, -m, -Q, -q, -S, or -s options are specified, information about all active IPC facilities is listed.
RESTRICTIONS
System data structures may change while ipcs is running; the output of ipcs is not guaranteed to be consistent.
BUGS
This manual page is woefully incomplete, because it does not at all attempt to explain the information printed by ipcs.
SEE ALSO
ipcrm(1)
AUTHORS
Thorsten Lockert <tholo@sigmasoft.com>
BSD
June 18, 1994 BSD