06-07-2010
Zaxxon/Corona688, When I log in as root and change the ulimit, it remains as I have changed. But the next day it changes back to the wrong Ulimit.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i've encountered the following problem with sco unixware7.
after using the "ulimit -f unlimited" command and then using "ulimit -a" it lists the filesize as unlimited.
BUT, when type the ulimit command without parameters, the output is given as 4194303
so i can't create a file bigger than... (4 Replies)
Discussion started by: roydv
4 Replies
2. 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
3. Programming
I would like to know where is the ulimit value stored in the shell. And how to get or modify it using the C program.
I run the command ulimit it shows me unlimited and quits.
Where that value is stored.
Thanks (1 Reply)
Discussion started by: mobile01
1 Replies
4. Shell Programming and Scripting
How do i set ulimit for user (4 Replies)
Discussion started by: Krrishv
4 Replies
5. SCO
hi,
i cant set ULIMIT for normal user (file size more than 2gb).but in root user it is working fine.in user it is giving error like "limit exceeded (priviledged user)". (2 Replies)
Discussion started by: prakrithi
2 Replies
6. 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
7. 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
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. AIX
Hi,
Our application team is asking me to set ulimit parameter in my AIX 6.1 TL8 box.
Some of them i set already.
address space limit (kbytes) (-M) unlimited
locks (-L) unlimited
locked address space (kbytes) (-l) 64
nice (-e) ... (3 Replies)
Discussion started by: sunnybee
3 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 OPENSOLARIS
fchroot
chroot(2) System Calls chroot(2)
NAME
chroot, fchroot - change root directory
SYNOPSIS
#include <unistd.h>
int chroot(const char *path);
int fchroot(int fildes);
DESCRIPTION
The chroot() and fchroot() functions cause a directory to become the root directory, the starting point for path searches for path names
beginning with / (slash). The user's working directory is unaffected by the chroot() and fchroot() functions.
The path argument points to a path name naming a directory. The fildes argument to fchroot() is the open file descriptor of the directory
which is to become the root.
The privilege {PRIV_PROC_CHROOT} must be asserted in the effective set of the process to change the root directory. While it is always pos-
sible to change to the system root using the fchroot() function, it is not guaranteed to succeed in any other case, even if fildes is valid
in all respects.
The ".." entry in the root directory is interpreted to mean the root directory itself. Therefore, ".." cannot be used to access files out-
side the subtree rooted at the root directory. Instead, fchroot() can be used to reset the root to a directory that was opened before the
root directory was changed.
RETURN VALUES
Upon successful completion, 0 is returned. Otherwise, -1 is returned, the root directory remains unchanged, and errno is set to indicate
the error.
ERRORS
The chroot() function will fail if:
EACCES Search permission is denied for a component of the path prefix of dirname, or search permission is denied for the directory
referred to by dirname.
EBADF The descriptor is not valid.
EFAULT The path argument points to an illegal address.
EINVAL The fchroot() function attempted to change to a directory the is not the system root and external circumstances do not
allow this.
EINTR A signal was caught during the execution of the chroot() function.
EIO An I/O error occurred while reading from or writing to the file system.
ELOOP Too many symbolic links were encountered in translating path.
ENAMETOOLONG The length of the path argument exceeds PATH_MAX, or the length of a path component exceeds NAME_MAX while _POSIX_NO_TRUNC
is in effect.
ENOENT The named directory does not exist or is a null pathname.
ENOLINK The path argument points to a remote machine and the link to that machine is no longer active.
ENOTDIR Any component of the path name is not a directory.
EPERM The {PRIV_PROC_CHROOT} privilege is not asserted in the effective set of the calling process.
SEE ALSO
chroot(1M), chdir(2), privileges(5)
WARNINGS
The only use of fchroot() that is appropriate is to change back to the system root.
SunOS 5.11 20 Jan 2003 chroot(2)