These limits apply to the Unix user that owns this virtual server and all sub-servers. They use systemd user slices, so they cap total usage across all processes for that user, including SSH logins and scripts
seems reasonably clear that it applies per VS and its sub-servers.
I have pro and I know I can manually set them on every Virtual Server but I wante to know if there was a way like cpanel where you set the package and then it applied to all in that package etc..
or move Administrator's Webmin modules out of the server templates by specifying a feature set.
@Jamie and @Ilia already agree that this is the wrong place for Administrator's Webmin modules and this is already being read by accounts rather than changes being pushed.
and @jimr I was just saying to @Stegan my thoughts on how cpanel works to better understand the relevance of my question. I do not need to have snide comments all the time.
I’m sure Resource Limits are in Server Templates or Account Plans or somewhere. It wouldn’t make sense to require individual configuration per virtual server. @Ilia how does one configure resource limit defaults?
Oh, wait, but you mean for existing virtual servers? That’s probably a job for the CLI, though I can’t find any docs that discuss the new resource limit features, only the old ones (which are incomprehensible to most people and probably not worth the trouble to use).
The reason people use Virtualmin is they are not good at the CLI. (i.e. me). Though I do understand some admins love the CLI.
Per User Packages and features would fix this and many other issues. - Set these options once at the package level and then all accounts get it. Anyway I will get of my soapbox
I get you … but also, there is a limit to the amount of complexity we can add to the UI. Hence the CLI exists for admins who want to script more complex operations.
That said, resource limits should absolutely be definable at the template level.
My proposal of packages (Account Plans) and features reduces complexity. Virtualmin is unique by having server templates (which can be very good for app deployment) but you merge things into server templates that should be hived of into packages and features. Virtulamin should have 3 things that control accounts. This scenario leads to extra complexity.
server templates = for setting up
packages = server resource limits and configurations. You call these Account Plans
features = what features and things a user can do
I am sure you guys have removed Save and Apply in edit account plan effectively making packages. So when edits are made on a package Account Planit is applied to all belonging to it.. If this is the case then these Resource Limits should go in here. I don’t think they should also go under Manage Virtual Server unless you specifically need to have an override feature. IF you did this should be a permission set in my proposed feature thing.
Some stuff in Account Plans do need moving out in to a separate features thing.
This is 100% needed for those admins who need to do that sort of stuff.
and I know I can manually set them on every Virtual Server but I wante to know if there was a way like cpanel where you set the package and then it applied to all in that package etc..
to me
