01-01-2020
Greetings and Happy New Year!
You can't judge like that what is good/bad...
Oracle is no ordinary user: many users access to files using oracle UID the same for processes etc
So it will depend on the size of your RDBMS or how many instances you have running on a server, how many processes are "oracle" etc the same for files and file size: no ordinary user would produce a file on a system the size of a full export (oracle)...
Why unlimited as value is not a good idea unless you know what you are doing AND what the others do:
Just an example: if a coder badly checked his new code that went in production ( or just a bug...) fall on a case you case have files opening but not closed correctly, worse though quite funny when it occurs: executing an infinite loop opening new processes...
You end with a freeze of the system where if lucky and an admin can connect will shutdown gracefully the box, more severe no one can connect and you have no other choice but to power off...
AIX at least lets you define on a specific user basis, may not be the case of all Unixes you see
Addendum:
Q: Do you have any issues? Giving a lot of resources will give you peace ( no errors or warning of running out of resources...) only that waste of resource will affect performance, if that is OK with you and production are happy, well why worry except for the case you do have an issue, it will be in proportion with what you gave
Last edited by vbe; 01-01-2020 at 05:29 AM..
Reason: Typos and addendum
This User Gave Thanks to vbe For This Post:
10 More Discussions You Might Find Interesting
1. AIX
Hi,
I have a query that suppose the first or last name of the user changes and we need to change its userid for aix too. Then in that case how do we handle this scenario??I guess we can't change the user id so we should re-create the new id and associate all the data of the old id. But I donno... (1 Reply)
Discussion started by: tintin@10
1 Replies
2. UNIX for Dummies Questions & Answers
ulimit -a gives the following output:$ulimit -a
time(seconds) unlimited
file(blocks) 2097152
data(kbytes) 131072
stack(kbytes) 16384
memory(kbytes) unlimited
coredump(blocks) 32768
nofiles(descriptors) 400
vmemory(kbytes) 147456
Abot output... (3 Replies)
Discussion started by: nervous
3 Replies
3. AIX
how to set the ulimit on AIX 5.2 version? (3 Replies)
Discussion started by: Shilpi
3 Replies
4. AIX
Hi Guys,
How do I increase the filesize ulimit for user jf01474, using the same value as of user oracle?
Ex: /etc/security/limits
default:
fsize = 4194302
core = 2097151
cpu = -1
data = 262144
rss = 65536
stack = 65536
... (3 Replies)
Discussion started by: sky_lark02
3 Replies
5. HP-UX
Hi,
on HP-UX when I run command
ulimit -a
I get
time(seconds) 4096
file(blocks) unlimited
data(kbytes) 1048576
stack(kbytes) 8192
memory(kbytes) unlimited
coredump(blocks) 4194303
nofiles(descriptors) 4096
Now I want to change
file(blocks) ... (2 Replies)
Discussion started by: namita.mundada
2 Replies
6. UNIX for Dummies Questions & Answers
Hello AIX gurus,
I have a requirement where I have to change user ID of user "myuser" from 100 to 200 and also the group ID of "mygroup" from 2 to 3. Please note that "myuser" has "mygroup" as it's primary group.
What steps do I need to follow for this and in what order? Also can you please... (2 Replies)
Discussion started by: sacguy08
2 Replies
7. 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
8. UNIX for Dummies Questions & Answers
Hello All,
If a user in AIX is locked due to multiple failed login attempts. How do I find out the IP address from where failed attempts were made?
regards,
Roshni (0 Replies)
Discussion started by: RoshniMehta
0 Replies
9. 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
10. AIX
Hi,
what are the ideal/best/recommended ulimit settings for a root user in AIX?
I understand that it depends on our environment. But I would like to know...what are settings you guys use in your environment for best performance.
default:
fsize = 2097151
core = 2097151
... (8 Replies)
Discussion started by: System Admin 77
8 Replies
LEARN ABOUT MOJAVE
shutdown
SHUTDOWN(8) BSD System Manager's Manual SHUTDOWN(8)
NAME
shutdown -- close down the system at a given time
SYNOPSIS
shutdown [-] [-h [-u] | -r | -s | -k] [-o [-n]] time [warning-message ...]
DESCRIPTION
The shutdown utility provides an automated shutdown procedure for super-users to nicely notify users when the system is shutting down, saving
them from system administrators, hackers, and gurus, who would otherwise not bother with such niceties.
The following options are available:
-h The system is halted at the specified time.
-k Kick everybody off. The -k option does not actually halt the system, but leaves the system multi-user with logins disabled (for all
but super-user).
-n If the -o is specified, prevent the file system cache from being flushed by passing -n option to halt(8) or reboot(8). This option
should probably not be used.
-o If -h or -r is specified, shutdown will execute halt(8) or reboot(8) instead of sending a signal to launchd(8).
-r The system is rebooted at the specified time.
-s The system is put to sleep at the specified time.
-u The system is halted up until the point of removing system power, but waits before removing power for 5 minutes so that an external
UPS (uninterruptible power supply) can forcibly remove power. This simulates a dirty shutdown to permit a later automatic power on.
OS X uses this mode automatically with supported UPSs in emergency shutdowns.
time Time is the time at which shutdown will bring the system down and may be the word now (indicating an immediate shutdown) or specify a
future time in one of two formats: +number, or yymmddhhmm, where the year, month, and day may be defaulted to the current system val-
ues. The first form brings the system down in number minutes and the second at the absolute time specified.
warning-message
Any other arguments comprise the warning message that is broadcast to users currently logged into the system.
- If '-' is supplied as an option, the warning message is read from the standard input.
At intervals, becoming more frequent as apocalypse approaches and starting at ten hours before shutdown, warning messages are displayed on
the terminals of all users logged in.
At shutdown time a message is written to the system log, containing the time of shutdown, the person who initiated the shutdown and the rea-
son. Corresponding signal is then sent to launchd(8) to respectively halt, reboot or bring the system down to single-user state (depending
on the above options).
A scheduled shutdown can be canceled by killing the shutdown process (a SIGTERM should suffice).
SIGTERM TO SIGKILL INTERVAL
Upon shutdown, all running processes are sent a SIGTERM followed by a SIGKILL. The SIGKILL will follow the SIGTERM by an intentionally inde-
terminate period of time. Programs are expected to take only enough time to flush all dirty data and exit. Developers are encouraged to
file a bug with the OS vendor, should they encounter an issue with this functionality.
SEE ALSO
kill(1), login(1), wall(1), halt(8), launchd(8), reboot(8)
BACKWARD COMPATIBILITY
The hours and minutes in the second time format may be separated by a colon (``:'') for backward compatibility.
HISTORY
The shutdown utility appeared in 4.0BSD.
BSD
December 11, 1998 BSD