Thanks a million. It is not worth to bundling everything together and making a combined version, but if you do not read the whole mail list archive, you will never know which features peruser offer. Next point is that admins like me are not able to know the order patches have to applied. So one goal should be to provide an overview of all available patches and how they should be applied. next step would be a 0.4 release with all the patches included. The documentation base of this project is not as good as it should be and so it is really hard for interested testers like me to integrate the patch in a testing or productive environment.
Personally I will use the patch for my productive servers and I want to use it with all available features. But currently I do neighter really know which features peruser offer nor where I can find a suitable documentation. As allready mentioned I will create a documentation including test szenarios and configuration reference on my website and if nescessary, I will also create a new version of the patch for testers but I will only be able to put the things togehter, if the developers of peruser and the patches will help me. On Thu, 12 Mar 2009 09:30:42 +0000, "[email protected]" <[email protected]> wrote: > Attached is the pam_limits patch, it should apply after the dc2 patch... > > You need to create a pam config file for peruser, i have the following > in /etc/pam.d/peruser: > > session required pam_limits.so > > I couldn't find the original email, so i tried to quickly extract it > from the source tree i had laying around. > > Looking back through the mail archives it seems there were a few misc > patches posted by various people... Is it worth bundling everything > together and making a combined version for people to test more easily? > -- web: http://www.mephisto23.com _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
