Tried setting up 2 diffrent policies, one for the "catch all" for all users and one for users that have specific quotas set. Set the priority for the catch all to 20 and the specific users one to 10. Still seems to be doing both. Now it seems to do them in the correct order .. user quota then all users but its still doing both... Is there some way to tell it if it matches the first policy then to not move on to the next policy?I'll add this to the TODO list, it was never a scenario I contemplated.In the interim you'll need to exclude users from the policy, by adding them to a group and going !%usergroup or something on those lines.You can then even use %usergroup in your other policy to explicitly set the quotas higher or lower, this way it will only match one of the policies and be configurable in 1 place.This was something that policyd v1 did by default.
v2 uses a totally different and much more flexible engine to resolve policies than v1.
sucks that it doesnt work the same way in v2.
v1 never had a policy engine in the sense of the one implemented in v2, I have taken literally months in time porting over functionality to v2 and ensuring it runs fast and efficiently and imposes little (if no, or even less load compared to v1) on the host system. At the same time many users of v1 have helped in the requirements and testing for v2, they've sponsored test hardware, testing resources, replacement hardware when my RAID array blew up, time and effort which has really helped in the development of v2. I am forever in debt to them :)
From my point of view it sucks there were not more involved with more broader requirements, if there were, the feature you're after would more than likely have been included by now. What you need is a simple field in the DB, two or three simple additions to the web interface, small policy engine change ... very easy, but cannot go into 2.0.x as its a major change regarding a core component. I will however be spinning off the 2.1 branch as soon as the dust settles and working on implementing the TODO list. v2.1 will include the functionality you're after.
Unfortunately with everyone that helped in the development of v2, no one had a requirement or test case to ensure v2 contains the specific feature you're after.
If you want to contribute, feel free to join the devel mailing list and join us on IRC.
Since this is not a feature in v2 do you think there is any way I can getyou to help me with some problems we are running into regarding version 1 or is that not supported on this list anymore?
v1 is definitely supported on this list and will be until such time as v2 has ALL the functionality of v1 and there is a clear migration path (which will be no time soon), so ask away. :)
-N
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
