%ulimit -a
nofiles(descriptors) 1024
This means that I can open up to 1024 file per process? But wonder if there is any hardlimit imposed by Solaris 2.6 (eg 255) ?
By the way, is there any tool that can trace which files (or sockets) are opened by a process?
Thanks
DY (5 Replies)
Hello,
I'm trying to login to an Oracle databse without entering the user/passwd. The server resides on an AIX 5.1 system, and using LDAP. I'm entering the following command
>sqlplus / @ORACLE_SID
This should work but for some odd reason I get a login denied.
But if I enter the user id... (1 Reply)
Hi,
I want to search particular pattern and splitting the file in to multiple files. (Splitted files may be more than 150). It got splitted upto 20 files after that, I got some error.
nawk: filename.21 makes too many open files.
input record number 654, file xxxxxxx
Can u guide me to... (1 Reply)
HI,
To restrict the number of files and number of processes used the user we use the following configuration in the file /etc/security/limits.conf.
oracle soft nofile 65572
oracle hard nofile 65572
oracle soft noproc 16384
oracle soft noproc 16384
My question is what do the 'soft' and... (1 Reply)
Hi,
How can we set per user core file size, etc in solaris, i.e. I want solaris counterpart/equivalent of linux /etc/security/limits.conf.
TIA (0 Replies)
Hi there,
I am trying to set a ulimit max in the /etc/security/limits.conf against a NIS netgroup (which contains a whole bunch of users) instead of a local user or group.
so I have a NIS netgroup called +@myusers , none of whose users are defined locally on the box. I want to ensure that... (2 Replies)
Hi,
I would like to know, how can I set limits (noproc,fsize,core, data...) to users in solaris, i.e. I want solaris counterpart/equivalent of linux /etc/security/limits.conf
Thanks!! (0 Replies)
Hello,
I have changed the value for one user in /etc/security/limit via root user
as paul:
time(seconds) unlimited
file(blocks) 2097151
data(kbytes) unlimited
stack(kbytes) unlimited
memory(kbytes) unlimited
coredump(blocks) unlimited
... (3 Replies)
OS version : RHEL 6.5
Below is an excerpt from /etc/security/limits.conf file for OS User named appusr in our server
appusr soft nproc 2047
appusr hard nproc 16384
What will happen if appusr has already spawned 2047 processes and wants to spawn 2048th process ?
I just want to know... (3 Replies)
Discussion started by: kraljic
3 Replies
LEARN ABOUT OSF1
sh
sh(1) General Commands Manual sh(1)NAME
sh - Shell, the standard command language interpreter
DESCRIPTION
[Tru64 UNIX] Tru64 UNIX provides two command interpreters with the name sh. The XCU5.0 and POSIX.2 compliant command interpreter sh is
available in the file /usr/bin/posix/sh and is described in the sh(1p) reference page. The Bourne shell, historically known as sh, is
available in the file /usr/bin/sh and is described in the sh(1b) reference page.
[Tru64 UNIX] Your initial, or login, shell is determined by your entry in the file /etc/passwd. This file can be changed only by your sys-
tem administrator. You must use whatever procedures are in place at your location to have this entry changed.
[Tru64 UNIX] If available on your system, you may use the passwd -s or the chsh commands to change your login shell.
Note
This option is not available if your site manages passwords through the Network Information Service (NIS) facility. Check with your system
administrator.
[Tru64 UNIX] Subsequent shells spawned from the initial shell depend on the value in the environment variable BIN_SH. If this variable is
set to xpg4, the POSIX shell is started. If this variable is set to svr4, an SVR4 compliant version of the shell is started. If this vari-
able is unset, the Bourne shell is started. If this variable is set to any other value, an error is reported and the results are unpre-
dictable. See the EXAMPLES section for information on setting this variable.
NOTES
[Tru64 UNIX] With Tru64 UNIX Version 4.0 the Korn shell, /usr/bin/ksh is the same as the POSIX shell /usr/bin/posix/sh.
RESTRICTIONS
[Tru64 UNIX] The file /etc/shells must include entries for both the POSIX shell /usr/bin/posix/sh and the Bourne shell, /usr/bin/sh. If
this file is incorrect, see your system administrator.
EXAMPLES
Using the Bourne, Korn, or POSIX shell, to set the variable BIN_SH to use the POSIX/ XCU5.0compliant shell, enter: BIN_SH=xpg4 export
BIN_SH Using the Bourne, Korn, or POSIX shell, to set the variable BIN_SH to use the SVR4 compliant shell, enter: BIN_SH=svr4 export BIN_SH
Using the Bourne, Korn, or POSIX shell, to unset the variable BIN_SH, enter: unset BIN_SH Using the C/ shell, to set the variable BIN_SH to
use the POSIX/XCU5.0 compliant shell, enter: setenv BIN_SH xpg4 Using the C/ shell, to set the variable BIN_SH to use the SVR4 compliant
shell, enter: setenv BIN_SH svr4 Using the C/ shell, to unset the variable BIN_SH, enter: unsetenv BIN_SH
FILES
User profile. Contains user information, including the login shell name. Contains the names of available and permitted shells.
SEE ALSO
Commands: csh(1), ksh(1), Bourne shell sh(1b), POSIX shell sh(1p), passwd(1)
Files: passwd(4), shells(4)
Standards: standards(5)sh(1)