Post by
Fatih AYHAN
Status
accepted
Current Situation:
Customers can add unlimited cron jobs regardless of package limits. There is no option to restrict cron job creation per package or per user.
This can result in:
- Uncontrolled server resource usage
- Operational monitoring and abuse challenges
Problem:
- In reseller, sub-reseller, and multi-customer environments, the inability to limit cron jobs per package creates risks.
- Administrators have no straightforward way to enforce per-package restrictions on cron job usage.
Proposed Feature:
- Add package-level control for cron jobs.
- Admins should be able to:
Enable / Disable cron job access per package
Set a numeric limit (0 / 1 / X jobs) per package - Changes should be applied automatically for both new and existing users.
Benefit:
- Enables consistent control for multi-customer setups.
- Supports proper resource management across the platform.
Comments :
No comments yet.
Search
Recent Feature Requests
Advanced DNS Panel: Bulk Updates, API Access, and Permission Controls
4 days, 6 hours ago
Posted by, Fatih AYHAN
Domain Alias (Parked Domain) Package Control
4 days, 6 hours ago
Posted by, Fatih AYHAN
OpenLiteSpeed 1.8 - Support for OpenLiteSpeed 1.8 in Eenos
1 month, 2 weeks ago
Posted by, Ellis Monroe
Phusion Passenger 6.0.27 - Support for Phusion Passenger 6.0.27 in Eenos
1 month, 2 weeks ago
Posted by, Ellis Monroe
Ruby 3.4.7 - Support for Ruby 3.4.7 in Eenos
1 month, 2 weeks ago
Posted by, Ellis Monroe
Ruby 3.3.10 - Support for Ruby 3.3.10 in Eenos
1 month, 2 weeks ago
Posted by, Ellis Monroe
Ruby 3.2.9 - Support for Ruby 3.2.9 in Eenos
1 month, 2 weeks ago
Posted by, Ellis Monroe
Ruby 4 - Support for Ruby 4 in Eenos
1 month, 2 weeks ago
Posted by, Ellis Monroe
OpenSSL 3.5 LTS
1 month, 2 weeks ago
Posted by, Ellis Monroe
Upgrade libuv to version v1.51.0 for enhanced performance, stability, and security
1 month, 2 weeks ago
Posted by, Ellis Monroe