-bash:ulimit:max User Processes:cannot Modify limit:operation not permitted

When you install Oracle, when you create an Oracle user, the following error is reported when switching Oracle users

[Email protected] ~]# su-oracle
-bash:ulimit:max User Processes:cannot Modify limit:operation not permitted

After viewing the result is forget to modify/etc/security/limits.conf

About/etc/security/limits.conf interpretation and application, see I reprint the following article

The limits.conf format is as follows:
username| @groupname Type Resource limit

username| @groupname: Sets the user name that needs to be restricted, the group name is preceded by the @ and the user name differs. You can also use the wildcard character * to restrict all users.

Type: Soft,hard and-,soft refer to the setting values that are currently in effect for the system. Hard indicates the maximum value that can be set in the system. The soft limit cannot be higher than the Har limit. -The soft and hard values are also set.

Resource
Core-limits the size of the kernel file
Date-Maximum data size
Fsize-Maximum file size
Memlock-Maximum lock memory address space
Nofile-Maximum number of open files
RSS-Maximum Persistent setting size
Stack-Maximum stack size
CPU-Maximum CPU time in minutes
Noproc-Maximum number of processes
As-address space limitations
Maxlogins-Maximum number of logons allowed by this user

For the limits.conf file configuration to take effect, you must make sure that the pam_limits.so file is added to the startup file. The view/etc/pam.d/login file has:
Session required/lib/security/pam_limits.so

Temporarily, applies to a shell session that is logged on through the Ulimit command.
Permanently, by adding a corresponding Ulimit statement to one of the files read by the login shell (for example, ~/.profile), the shell-specific user resource file, or by editing the/etc/security/limits.conf.
What is a core file that, when a program crashes, copies the stored image of the process in the core file of the current working directory of the process. The core file is simply a memory image (plus debugging information), which is used primarily for debugging purposes. The core file is a
Binaries, you need to use the appropriate tools to analyze the memory image of the program when it crashes.

The system default core file size is 0, so it is not created. You can use the Ulimit command to view and modify the size of the core file.

$ulimit-C

0

$ ulimit-c 1000

$ ulimit-c

1000

-c Specifies the size of the core file to be modified, and 1000 specifies the core file size. You can also make no restrictions on the size of the core file, such as:

# ulimit-c Unlimited

#ulimit-C

Unlimited

If you want the modification to take effect permanently, you need to modify the configuration file, such as. Bash_profile,/etc/profile, or/etc/security/limits.conf.

2.nofile-Maximum number of open files

For applications that need to make many socket connections and leave them open, it is best to set the number of file descriptors higher than the default values for the user by using Ulimit–n or by setting the Nofile parameter.

Vi/etc/security/limits.conf
* Soft Nofile 10240 #软限制

* Hard Nofile 10240 #硬限制
The ulimit-n 2048 modification is valid only for the current shell and expires after exiting:
If a program has already run, at this time ulimit-n is 1024, then ulimit-n 2048, then run the B program, exit the current shell user, the shell again, then run C program, then only B program with 2048, the other used is 1024

[Email protected] ~]# vim/etc/security/limits.conf

Add the following content

Oracle Soft Nproc 2047
Oracle Hard Nproc 16384
Oracle Soft Nofile 1024
Oracle Hard Nofile 65536

The problem has been solved

http://blog.csdn.net/evils798/article/details/7991431

Http://docs.oracle.com/cd/E11882_01/install.112/e24326/toc.htm#CEGIHDBF

-bash:ulimit:max User Processes:cannot Modify limit:operation not permitted