10-25-2012
AFAIK the limits are set when a session starts, so you probably have to log in again as "paul" to see the new limits in effect.
In general, using "chsec" as funksen said, is the preferable way to do these things in AIX.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi! All,
This is True64 Unix, 4.0.F patch kit 4
I have a 15GB Oracle dump file that I have to backup to tape. I am trying to use "tar" to dump it to tape, but
tar complained that the file was too big and that it was
truncating it!.
I am compressing the file using the "compress" utility.... (3 Replies)
Discussion started by: sdharmap
3 Replies
2. UNIX for Dummies Questions & Answers
What command(s) do I use to change the security on a file? I need to change the owner as well as read write end execute options. (5 Replies)
Discussion started by: ekkehard
5 Replies
3. UNIX for Advanced & Expert Users
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)
Discussion started by: praveen_b744
1 Replies
4. Solaris
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)
Discussion started by: slash_blog
0 Replies
5. UNIX for Dummies Questions & Answers
Hi there,
I am working on AIX and i dont have permission for /etc/security/limits file.
In the man page of ulimit it is mentioned that it will get the limitations for me from /etc/security/limits file.
the file permission for ulimit command is
-r-xr-xr-x 15 bin bin ... (6 Replies)
Discussion started by: quintet
6 Replies
6. AIX
Dears
Security users in AIX don’t have permission to change the group of the user thru Smitty Users
When they try to change the group of the users to any group they'll get permission denied
Security profile in Smitty :
User... (10 Replies)
Discussion started by: ITHelper
10 Replies
7. Linux
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)
Discussion started by: rethink
2 Replies
8. Solaris
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)
Discussion started by: kiekurt
0 Replies
9. UNIX for Dummies Questions & Answers
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
10. Programming
Hi All,
I am getting below run time error
I checked the code and see the structure defined as below and using the file position variable
typedef struct Get_file {
char *current_pathname;
unsigned int tot_bytes_io, physical_position;
int... (2 Replies)
Discussion started by: arunkumar_mca
2 Replies
LEARN ABOUT REDHAT
faillog
FAILLOG(8) System Manager's Manual FAILLOG(8)
NAME
faillog - examine faillog and set login failure limits
SYNOPSIS
faillog [-u login-name] [-a] [-t days]
[-m max] [-pr]
DESCRIPTION
faillog formats the contents of the failure log, /var/log/faillog, and maintains failure counts and limits. The order of the arguments to
faillog is significant. Each argument is processed immediately in the order given.
The -p flag causes failure entries to be printed in UID order. Entering -u login-name flag will cause the failure record for login-name
only to be printed. Entering -t days will cause only the failures more recent than days to be printed. The -t flag overrides the use of
-u. The -a flag causes all users to be selected. When used with the -p flag, this option selects all users who have ever had a login
failure. It is meaningless with the -r flag.
The -r flag is used to reset the count of login failures. Write access to /var/log/faillog is required for this option. Entering -u
login-name will cause only the failure count for login-name to be reset.
The -m flag is used to set the maximum number of login failures before the account is disabled. Write access to /var/log/faillog is
required for this option. Entering -m max will cause all accounts to be disabled after max failed logins occur. This may be modified with
-u login-name to limit this function to login-name only. Selecting a max value of 0 has the effect of not placing a limit on the number of
failed logins. The maximum failure count should always be 0 for root to prevent a denial of services attack against the system.
Options may be combined in virtually any fashion. Each -p, -r, and -m option will cause immediate execution using any -u or -t modifier.
CAVEATS
faillog only prints out users with no successful login since the last failure. To print out a user who has had a successful login since
their last failure, you must explicitly request the user with the -u flag, or print out all users with the -a flag.
Some systems may replace /var/log with /var/adm or /usr/adm.
FILES
/var/log/faillog - failure logging file
SEE ALSO
login(1), faillog(5)
AUTHOR
Julianne Frances Haugh (jockgrrl@ix.netcom.com)
FAILLOG(8)