* Grzegorz Pawel Szostak said: > > > /bin/lshell/bash it will work always ? Am i wrong ? > > I don't understand what you mean? Is it that you want to force every user to > > use bash? Well, you can, but they have the right to change their shells. > > Playing BOFH is not always justified :)) > You are right, my question is: > If in /etc/passwd file user has in shell field an bash shell, and if s/he > after login will change his/her shell environment (limits) that is in bash > will be in ksh, etc.. ? If you're using lshell, yes. If you're using ulimit, no. If you use PAM, yes. > > > > and setup a cronjob that will remake the database every hour or so, and > > > > remember to remake the database every time you add a new user :)). > > > ... partial sollution ;) i have a lot of job. Better is to write module or > > Why a partial solution? If you use adduser, then create > > /usr/local/sbin/adduser.local script that invokes 'make -C /var/lib/misc', > > setup a crontab and forget about the thing... > And all programs (ssh, pop, ...) will work ? Yes. They all use getpwent or derivatives and they in turn use the NSS libaries - that's, of course, if you use glibc. So they will work flawlessly. > > What for? kernel implements everything you need (man setrlimit), you just > > need a program to set the limits for you. Test the debian/potato PAM - it > > does it allright. > I've tested PAM with lshell and it wasn't working ... Hmm... it works for me just fine. marek
Attachment:
pgpkhc2rfDKLj.pgp
Description: PGP signature