Hi, first of all I apologize if I posted this thread in a wrong group, yet since I am not day by day user of KDE everything is quite new to me .

Well, I am using Slackware which means it does not have PAM installed but for limiting user resource I use part of shadow package namely /etc/limits file which basically does the same as /etc/security/limits.conf in PAM systems. This method is ok as long as i do not use kdm as a session manager. If i use kdm for logging, the limits defined in /etc/limits are ignored and magically lower default values are assigned to virtual terminals.

Could tell me if kdm should understand /etc/limits or how to force it to use this method of limiting resources?

I tried to read all the config files which seem to belong to kdm yet so far i did not succeed to have it work.

Thank you for any help.
I'm running Slackware 12.2 with KDE 3.5.10.
Kind regards.

--
luk

lukaswu wrote:Hi, first of all I apologize if I posted this thread in a wrong group, yet since I am not day by day user of KDE everything is quite new to me .

Well, I am using Slackware which means it does not have PAM installed but for limiting user resource I use part of shadow package namely /etc/limits file which basically does the same as /etc/security/limits.conf in PAM systems. This method is ok as long as i do not use kdm as a session manager. If i use kdm for logging, the limits defined in /etc/limits are ignored and magically lower default values are assigned to virtual terminals.

Could tell me if kdm should understand /etc/limits or how to force it to use this method of limiting resources?

I tried to read all the config files which seem to belong to kdm yet so far i did not succeed to have it work.

Thank you for any help.
I'm running Slackware 12.2 with KDE 3.5.10.
Kind regards.

--
luk

i have not had the full opportunity to test the suggestions i am about to make, i just want to give you more resources to investigate your search.

you should look into LOGIN.DEFS(5) and ULIMIT(3). in the /etc/login.defs file there is the shadow password configuration, and there is a line to set ULIMIT configurations. it is commented out by default. the syntax and usage of ulimit is not entirely straightforward, but it is a command as well, so you can mess around with it until you find the [limit] you want.

i hope this gets you moving a little more in the right direction.

Take care,

and i forgot to add other valuable resources
http://slackwiki.org/Resource_Limits

vbatts wrote:and i forgot to add other valuable resources
http://slackwiki.org/Resource_Limits

Thank you for the information, but I have seen all of these.

The only problem is that in /etc/limits file you describe limits per user and in inittscripts you place global values, which with additional acl makes it a work around not a real solution.

So I still insist that kdm uses regular /etc/limits file .

kind regards.

--
luk

This may be a limitation in current KDM, since it is likely used by distributions which do use PAM.