Displaying 5 results from an estimated 5 matches for "default_rul".
Did you mean:
default_rule
2014 Nov 21
2
[PATCH] [dovecot 2.2.9] Quota warnings ignored with FS quotas
...used:
1. percentage-based quota warnings, i.e.:
quota_warning = storage=1%% quota-warning 1 %u
2. filesystem quota backend (and probably others, except for quotas
configured directly in dovecot config)
Percentage-based quota warnings have rule.bytes_limit recalculated based
on root_set->default_rule.bytes_limit, however this value is zero when
FS quotas are in use. Real quota values (from quotactl) are fetched very
late, in quota_warnings_execute() but at that point no recalculation
happens. As the warning rules have bytes_limit==0, they're effectively
ignored.
The patch below enable...
2015 Mar 23
1
[PATCH] [dovecot 2.2.9] Quota warnings ignored with FS quotas
...quota_warning = storage=1%% quota-warning 1 %u
>>
>> 2. filesystem quota backend (and probably others, except for quotas
>> configured directly in dovecot config)
>>
>> Percentage-based quota warnings have rule.bytes_limit recalculated
>> based on root_set->default_rule.bytes_limit, however this value is
>> zero when FS quotas are in use. Real quota values (from quotactl) are
>> fetched very late, in quota_warnings_execute() but at that point no
>> recalculation happens. As the warning rules have bytes_limit==0,
>> they're effectiv...
2015 Feb 17
0
[PATCH] [dovecot 2.2.9] Quota warnings ignored with FS quotas
...nings, i.e.:
>
> quota_warning = storage=1%% quota-warning 1 %u
>
> 2. filesystem quota backend (and probably others, except for quotas
> configured directly in dovecot config)
>
> Percentage-based quota warnings have rule.bytes_limit recalculated
> based on root_set->default_rule.bytes_limit, however this value is
> zero when FS quotas are in use. Real quota values (from quotactl) are
> fetched very late, in quota_warnings_execute() but at that point no
> recalculation happens. As the warning rules have bytes_limit==0,
> they're effectively ignored.
>...
2012 Nov 29
2
[LLVMdev] problem trying to write an LLVM register-allocation pass
I have a new problem: Register RBP is used in a function foo. (I am not
allocating RBP to any virtual register, the instances of RBP in function
foo are in the machine code when my register allocator starts.)
Function foo calls function bar. Register RBP is not saved across the
call, though it is live after the call. Function bar includes a virtual
register. The code that I'm using to
2012 Dec 01
0
[LLVMdev] problem trying to write an LLVM register-allocation pass
...*program_name;
extern char *action_array;
extern int action_size;
extern int defs1_offset, prolog_offset, action_offset, action_index;
extern int onestate[500], onesym[500];
extern int onenext[500], onedef[500], onesp;
extern int current_mns, current_max_rules;
extern int num_rules, num_eof_rules, default_rule, lastnfa;
extern int *firstst, *lastst, *finalst, *transchar, *trans1, *trans2;
extern int *accptnum, *assoc_rule, *state_type;
extern int *rule_type, *rule_linenum, *rule_useful;
extern int current_state_type;
extern int variable_trailing_context_rules;
extern int numtemps, numprots, protprev[50]...