05-13-2014
Its always better to have unlimited for root, as its the boss.
Moreover, when you do operations as root, you need those values at higher range.
Example: To transfer huge file(s), you need files (blocks) at very high value or better unlimited, because it will stop the transfer after it reach the defined value.
So, keep the boss smiling and you will be happy too.
This User Gave Thanks to ibmtech For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
As a regular (non-root) user on Unix servers I'm accustomed to changing my .profile file to set paths that I frequently use, etc.
I am trying to learn unix and set up a test server running SunOS 5.8. When I login as root I don't see a .profile file that belongs to root wherein I could change the... (1 Reply)
Discussion started by: FredSmith
1 Replies
2. AIX
how to set the ulimit on AIX 5.2 version? (3 Replies)
Discussion started by: Shilpi
3 Replies
3. AIX
Hi all,
I cannt use 'su' to login to root or any other users though everything seems ok. I read some articles that says if you do recursive chmod 777 on /usr it can create this problem.
I did the same. can anybody tell me how to repair it. Any ideas will be appreciated.
thnks (7 Replies)
Discussion started by: itesh.dash
7 Replies
4. AIX
Hello,
How can I setup the ulimit for memory permanent
ulimit -m unlimited
ulimit -a Output from the ulimit command should be similar to the following:time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 2097152
stack(kbytes) 32768... (4 Replies)
Discussion started by: filosophizer
4 Replies
5. AIX
How to block the root user login in system direct console. Users should login with non-root ids themselves and then use the su command to become root. Which configuration file i need to check and disable it. (5 Replies)
Discussion started by: kmvinay
5 Replies
6. AIX
Hi,
I'm newbee to AIX and would like to setup a process which kills 1 Hr. ideal users from smit. Please advise for making it work. :)
Thanks,
Sumit (2 Replies)
Discussion started by: sumit30
2 Replies
7. UNIX for Dummies Questions & Answers
I've been through many threads before i decide to create a separate thread.
I can't really find the solution to my (simple) problem.
Here's what I'm trying to achieve:
As "canar" user I want to run a command, let's say "/opt/ocaml/bin/ocaml" as "duck" user.
The only to achieve this is to... (1 Reply)
Discussion started by: canar
1 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
Hello,
I am testing sudo and I want to test it. Can anyone please let me know few commands (of course other than shutdown, reboot etc. as I can't reboot the box) on AIX that can be run by ROOT only.
Thanks
---------- Post updated at 07:43 PM ---------- Previous update was at 07:38 PM... (5 Replies)
Discussion started by: prvnrk
5 Replies
10. UNIX for Advanced & Expert Users
I have seen two different ways for changing the ulimit for a user in aix. Which one is better?
Option 1
edit /etc/security/limits
oracle:
fsize = -1
data = -1
stack = -1
fsize_hard = -1
nofiles = -1
nofiles_hard = -1
Option 2
... (6 Replies)
Discussion started by: cokedude
6 Replies
LEARN ABOUT DEBIAN
bosskill
BOSSKILL(8) System Manager's Manual BOSSKILL(8)
NAME
bosskill - send a signal to your boss, or terminate your boss
SYNOPSIS
bosskill [ -signal ] <bossname>
DESCRIPTION
bosskill sends the TERM (terminate, 15) signal to the boss with the specified bossname. If a signal name or number preceded by `-' is
given as the first argument, that signal is sent instead of terminate. The killed boss must be in the system administrator's supervisory
chain.
The following is a list of all signals with names as in the include file <signal.h>:
SIGHUP 1 hangup. Forces bossname to re-read his/her job description and figure out that he/she knows squat about sysadmin work or
life, in general.
SIGINT 2 interrupt. Prevents the bossname from interrupting the sysadmin for one hour.
SIGQUIT 3 quit. Causes the boss to quit his/her job with no explanation.
SIGILL 4 illegal instruction. Makes the boss believe the last instruction he/she gave was illegal, so he/she withdraws it.
SIGTRAP 5 trace trap. Display the exact location of the boss.
SIGABRT 6 abort. Makes the boss go home and try again tomorrow.
SIGKILL 9 kill. Game over.
SIGBUS 10 bus error. Boss's transportation fails on the way to work.
SIGSEGV 11 segmentation violation. Boss realizes he/she is trying to do something for which he/she is not quailified and stops.
SIGSYS 12 bad argument. Boss loses.
SIGPIPE 13 smoke pipe. Boss samples some green leafy substance and mellows out.
SIGALRM 14 alarm. Boss is startled and falls over. Best used when boss is walking next to his/her boss.
SIGTERM 15 termination signal. Boss is fired.
BUGS
Sending a SIGABRT to a boss that is already home will cause him/her to walk aimlessly in circles for two hours.
HISTORY
Written by Eric L. Pederson <eric@bofh.org.uk>.
27 September 1995 BOSSKILL(8)