Define the upper bounds a reseller can allocate to their customer accounts. Access: root.

What this sets

• Package Name — letters, numbers, spaces only.
• Maximum Accounts — count of customer accounts the reseller may create (0 = unlimited).
• Maximum Disk Space — total pool in MB the reseller can distribute (0 = unlimited).
• Maximum % CPU per account — per-account CPU ceiling; 100% ≈ one full core.
• Maximum memory (RAM) per account — in MB.
• Maximum system processes per account — concurrent processes limit.
• Assigned IP Addresses — how many IPs the reseller may use/assign.
• Inodes limit (file limits) per account — max files/directories.
• I/O Disk Bandwidth per account — MB/s read/write cap.
• IOPS per account — operations-per-second cap.
• Permit Shell Access to accounts — allow the reseller to grant shell in their packages.
• Permit Unlimited Disk Space — allow the reseller to set “unlimited” disk in their packages.

Validation rules

• Package Name — must match ^[a-zA-Z0-9\s]+$.
• Maximum Accounts — 0–1,000,000.
• Maximum Disk Space (MB) — 0–1,000,000.
• Maximum % CPU — 0–1,000,000.
• Maximum memory (MB) — 0–1,000,000.
• Maximum processes — 0–1,000,000.
• Assigned IP Addresses — 0–1024.
• Inodes limit — 0–1,000,000,000.
• I/O Disk Bandwidth (MB/s) — 0–100,000.
• IOPS — 0–10,000.
• Permit Shell Access / Permit Unlimited Disk Space — 0 or 1.

What happens on save

• Inputs are validated; on error you’ll see a precise message and nothing is saved.
• On success, a new reseller package entry is created and stored for use when assigning reseller quotas.
• The form resets to defaults and the list view is reloaded to show the new package.

Practical guidance

• Use a realistic CPU% baseline (e.g., 200–300%) to allow bursts without enabling noisy neighbors.
• Keep memory and process limits aligned with your PHP-FPM policies.
• Set disk and inode quotas to prevent silent storage exhaustion.
• Grant “Permit Shell Access” only for trusted resellers; prefer jailed shells in their packages.