OS - Sun OS7
What sources can I go to to figure out what is the maximun number of processes for OS7 with 2GB of memory.
I believe it is 64K processes, but this number reflects resources being swaped.
Any help is appreciated
SmartJuniorUnix (1 Reply)
we've got solaris 5.6 installed in a ultra 5 box that serves as gateway server going to the main unix box.
just like to find out how to determine the number of concurrent terminal connections and processes that the ultra 5 box can handle? and handling at present time?
thanks in advance! (1 Reply)
Hi,
I notice in my Sun Solaris 8 sparc workstatin, I am able to login concurrently using a same user ID.
Is there a way to disallow this? That is, at anyone time, the user can have only 1 login session.
How can it be done?
Thanks (10 Replies)
Hi
I have a ksh that can have multiple instances running at the same time.
The script (each instance) uses the SAME log file to write to.
Should this cause a problem or is the ksh clever enough to queue write requests to the file?
Thanks.
GMMIKE (2 Replies)
Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go?
Thank you
Richard (4 Replies)
Hi
Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages.
Any free tools or scripts to do this?
Many thanks. (2 Replies)
Hi,
on normal (non concurrent) vgs, it's possible to extend a lun on san-storage , and use chvg -g to rewrite vgda, and use disks with the new size for lvm operations
is the same procedure possbile on a hacmp-cluster (2 node in our case) with concurrent vgs in active/passive mode?
cheers... (5 Replies)
Hi all,
I have a folder with sql files that need to be inserted in a DB with SQL*Plus. The thing is that it takes too long to insert them all one by one, so I want to insert them five at a time.
Currently what I use is this:
for $FILENAME in *.sql
do
sqlplus -s $DBUSER@$SID << EOF
... (0 Replies)
Hi,
The problem detail is follows
I have three individual scripts .
SCRIPT A
sh -x sqoop_channels_nc_daily_01.sh & sh -x sqoop_channels_nc_daily_02.sh & sh -x sqoop_channels_nc_daily_03.sh
SCRIPT B
sh -x sqoop_contacts_nc_daily_01.sh & sh -x sqoop_contacts_nc_daily_02.sh & sh -x... (1 Reply)
Hi,
What are the differences between concurrent and enhanced concurrent VGs.?
Any advantages of enhanced concurrent VG over normal concurrent vg
Regards,
Siva (2 Replies)
Discussion started by: ksgnathan
2 Replies
LEARN ABOUT ULTRIX
plock
plock(2) System Calls Manual plock(2)Name
plock - lock or unlock process, text, or data in memory
Syntax
#include <sys/lock.h>
int plock (op)
int op;
Description
The call allows the calling process to lock its text segment (text lock), its data segment (data lock), or both its text and data segments
(process lock) into memory. Locked segments are immune to page outs, and the process is immune to swap outs. The call also unlocks these
segments.
The op argument specifies the following:
PROCLOCK Lock text and data segments into memory (process lock)
TXTLOCK Lock text segment into memory (text lock)
DATLOCK Lock data segment into memory (data lock)
UNLOCK Remove locks
Return Values
Upon successful completion, a value of 0 is returned to the calling process. Otherwise, a value of -1 is returned, and errno is set to
indicate the error.
Diagnostics
The call fails under the following conditions:
[EPERM] The effective user ID of the calling process is not superuser.
[EINVAL] The op argument is equal to PROCLOCK, and a process lock, a text lock, or a data lock already exists on the calling process.
[EINVAL] The op argument is equal to TXTLOCK, and a text lock or a process lock already exists on the calling process.
[EINVAL] The op argument is equal to DATLOCK, and a data lock or a process lock already exists on the calling process.
[EINVAL] The op argument is equal to UNLOCK, and no type of lock exists on the calling process.
Restrictions
The effective user ID of the calling process must be superuser to use this call.
Both PROCLOCK and TXTLOCK lock the text segment of a process, and a locked text segment is locked for all sharing processes.
Because the effective user ID of the calling process is superuser, take care not to lock more virtual pages than can be contained in physi-
cal memory. A deadlock can result.
See Alsoexecve(2), exit(2), fork(2), shmctl(2)plock(2)