04-22-2014
Hi,
Alternatively, you can use the smit interface if you are in need of a simpler way of setting the "ulimits" - this has the added advantage of upgrading the database files as well where it's required.
Regards
Gull04
10 More Discussions You Might Find Interesting
1. Solaris
How do you make the ulimit values permanent for a user?
by default, the root login has the following ulimits:
# ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 1024
memory(kbytes)... (2 Replies)
Discussion started by: kiem
2 Replies
2. Shell Programming and Scripting
How do i set ulimit for user (4 Replies)
Discussion started by: Krrishv
4 Replies
3. UNIX for Advanced & Expert Users
I would like to set the maximum number or open files per process to be greater than 1024000 (for specific application scalability purpose). I am using RHEL 5.3/Ext4.
%sysctl fs.file-max
fs.file-max = 164766821
I also have added the folloing to /etc/security/limits.conf
* ... (7 Replies)
Discussion started by: Hsianglung Wu
7 Replies
4. UNIX for Advanced & Expert Users
I changed the standard Ulimit sometime back. But when I change it back, the setting does not get updated.
How do I make the change permanent
Waitstejo (7 Replies)
Discussion started by: Waitstejo
7 Replies
5. Solaris
how do i check the ulimit set on my server..
ca i know whats the command ??
thanks in advance .. (5 Replies)
Discussion started by: expert
5 Replies
6. UNIX for Advanced & Expert Users
All,
Our SA is considering setting the max open files from 2048 to 30K. This sounds like a drastic change. Does anybody have an idea of the negative impacts of increasing the open files too high? Would like to know if this change could negatively impact our system. What test should we run to... (2 Replies)
Discussion started by: wcrober
2 Replies
7. Solaris
Hello, could you help me please?
I write in command line: "ulimit 500"
-> i've set the max size of 512-bytes blocks that i can write in one file.
But when after it i use ulimit.3c in my program: "ulimit(UL_GETFSIZE);"
the result turns out 1000. Why is it so? They always differ so that one is... (2 Replies)
Discussion started by: Zhenya_
2 Replies
8. Red Hat
The root user runs the following
ulimit -a | grep open
and gets a result of
open files (-n) 8162
A user runs the same command and gets a result of
open files (-n) 2500
How can you set the ulimit of the user to... (2 Replies)
Discussion started by: jsanders
2 Replies
9. Solaris
Trying to figure out the best method of security for oracle user accounts. In Solaris 10 they are set as regular users but have nologin set forcing the dev's to login as themselves and then su to the oracle users.
In Solaris11 we have the option of making it a role because RBAC is enabled but... (1 Reply)
Discussion started by: os2mac
1 Replies
10. Solaris
A coredump is being created by one of our applications on Solaris server and occupying entire space on the mount, thereby bringing down the application.
While we try to identify the root cause, i tried to limit to limit the size of the core dump.
Executed below command in shell and also updated... (2 Replies)
Discussion started by: kesani
2 Replies
LEARN ABOUT CENTOS
groupd
GROUPD(8) cluster GROUPD(8)
NAME
groupd - compatibility daemon for fenced, dlm_controld and gfs_controld
SYNOPSIS
groupd [OPTIONS]
DESCRIPTION
The groupd daemon and libgroup library are used by the fenced, dlm_controld and gfs_controld daemons when they are operating in clus-
ter2-compatible mode to perform a rolling cluster upgrade from cluster2 to cluster3.
See cman(5) for more information on the upgrading configuration option needed to perform a rolling upgrade.
When the upgrading option is enabled, cman adds the following to the online configuration:
<group groupd_compat="1"/>
This setting causes the cman init script to start the groupd daemon, and causes the groupd, fenced, dlm_controld and gfs_controld daemons
to operate in the old cluster2 mode so they will be compatible with cluster2 nodes in the cluster that have not yet been upgraded.
The upgrading setting, including the groupd_compat setting, cannot be changed in a running cluster. The entire cluster must be taken off-
line to change these because the new cluster3 default modes are not compatible with the old cluster2 modes. The upgrading/compat settings
cause the new cluster3 daemons to run the old cluster2 code and protocols.
OPTIONS
Command line options override a corresponding setting in cluster.conf.
-D Enable debugging to stderr and don't fork.
-L Enable debugging to log file.
-g num groupd compatibility mode, 0 off, 1 on. Default 0.
-h Print a help message describing available options, then exit.
-V Print program version information, then exit.
SEE ALSO
cman(5), fenced(8), dlm_controld(8), gfs_controld(8)
cluster 2009-01-19 GROUPD(8)