Update information about limits #269
Conversation
|
|
||
| 1. **LVE Manager shows one thing, user files show another** | ||
| - **Symptoms**: <span class="notranslate">`/var/cpanel/packages/packagename`</span> has updated limits, but <span class="notranslate">`/var/cpanel/users/username`</span> shows old values | ||
| - **Resolution**: This is expected behavior. Check <span class="notranslate">`repquota`</span> for actual enforced limits |
There was a problem hiding this comment.
I think this discrepancy scenario is a straight duplication of what you described in "cPanel User File Synchronization". It's also explained as not an issue.
There was a problem hiding this comment.
@azheregelya You're right it's indeed duplication, removed this part.
|
|
||
| **Inode Limits Synchronization Issues** | ||
|
|
||
| If you notice discrepancies between different sources showing inode limits, this is likely due to the [known limitations](#known-limitations) of <span class="notranslate">cl-quota</span>. Here's how to troubleshoot: |
There was a problem hiding this comment.
I'm not sure that #known-limitations is an existing ref.
There was a problem hiding this comment.
@azheregelya Fixed, thanks for notice.
|
|
||
| If you notice discrepancies between different sources showing inode limits, this is likely due to the [known limitations](#known-limitations) of <span class="notranslate">cl-quota</span>. Here's how to troubleshoot: | ||
|
|
||
| **Verifying Actual Limits** |
There was a problem hiding this comment.
This is valuable part. I suggest to keep it with a name "How to check actual limits".
There was a problem hiding this comment.
@azheregelya agree, done!
| <span class="notranslate">cl-quota</span> has the following known limitations and behaviors that administrators should be aware of: | ||
| ::: | ||
|
|
||
| **cPanel User File Synchronization** |
There was a problem hiding this comment.
Why use **bold** markup instead of ##### headers ?
There was a problem hiding this comment.
@azheregelya Fixed. Changed all bold markup to proper #### headers as suggested.
| - **Resolution**: This is expected behavior. Check <span class="notranslate">`repquota`</span> for actual enforced limits | ||
| - **Verification**: Use WHM API or <span class="notranslate">`repquota`</span> to confirm working limits | ||
|
|
||
| 2. **Script to verify user package and actual limits via CLI** |
There was a problem hiding this comment.
This part can be merged with aforementioned Howto
There was a problem hiding this comment.
@azheregelya done.
NikolayVoina
force-pushed
the
Update-information-about-limits
branch
4 times, most recently
from
5de0e9b to
cd7561d
Compare
| @@ -3402,6 +3407,53 @@ cat /var/log/messages | grep clquota | |||
| You should not set soft limit higher than hard limit. cl-quota does not control it in any way, but in some cases, the system can ban such limits combination and they won’t be set or will be set in some other way. | |||
| ::: | |||
|
|
|||
| #### Known-cl-quota-limitations-behaviour | |||
There was a problem hiding this comment.
Is this intended to be written this way, with dashes in the title? How does this look in the final page?
There was a problem hiding this comment.
VuePress uses kebab-case for URL anchors but displays headings normally in the content.
| #### Known-cl-quota-limitations-behaviour | ||
|
|
||
| ::: tip Important | ||
| <span class="notranslate">cl-quota</span> has the following known limitations and behaviors |
There was a problem hiding this comment.
Aren't you making two intros here? If anything, the line about "known limitations and behaviors" seems redundant. Read this section out loud - does the flow of sentences make sense?
There was a problem hiding this comment.
You're right, we can get rid of the first intro and keep the second one. Now looks better ?
NikolayVoina
force-pushed
the
Update-information-about-limits
branch
from
cd7561d to
4e71fca
Compare
No description provided.