Re: pam_limits not effective

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



As i understand, there are problems with setting limits via pam.
Please, search this list for details - problem and its reasons were
discussed.

2005/11/8, Hannes Krueger <Hannes.Krueger@xxxxxxxxxx>:
> Hi out there,
>
> I tried to set some hard memory limits using /etc/secutity/limits.conf
> I set hard limits for my user for rss, data, stack, memlock 1000
> I also set a maxlogins of 4.
> I added "session required pam_limits.so" to /etc/pam.d/xdm and login.
>
> I was able to verify that the maxlogins limit works.
> all other limits seem to be without effect.
>
> Is there anything else to do?
> Are there any special requirements to the kernel?
>
> I'm using 2.6.5-7.201-default (Suse kernel)
>
> # Class Based Kernel Resource Management
> #
> CONFIG_CKRM=y
> CONFIG_RCFS_FS=m
> CONFIG_CKRM_TYPE_TASKCLASS=y
> CONFIG_CKRM_RES_NUMTASKS=m
> CONFIG_CKRM_CPU_SCHEDULE=y
> # CONFIG_CKRM_CPU_SCHEDULE_AT_BOOT is not set
> CONFIG_CKRM_RES_BLKIO=y
> CONFIG_CKRM_TYPE_SOCKETCLASS=y
> CONFIG_CKRM_RBCE=m
> CONFIG_CKRM_CRBCE=m
> CONFIG_DELAY_ACCT=y
> CONFIG_KALLSYMS=y
> CONFIG_FUTEX=y
> CONFIG_EPOLL=y
> CONFIG_IOSCHED_NOOP=y
> CONFIG_IOSCHED_AS=y
> CONFIG_IOSCHED_DEADLINE=y
> CONFIG_IOSCHED_CFQ=y
> CONFIG_IOSCHED_PS=y
> # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
>
> _______________________________________________
> 
> Pam-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/pam-list
>

_______________________________________________

Pam-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/pam-list

[Index of Archives]     [Fedora Users]     [Kernel]     [Red Hat Install]     [Linux for the blind]     [Gimp]

  Powered by Linux