-
-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add loginctl_user type/provider #131
Conversation
@raphink should this be documented in the README.md? |
Actually, before we release 2.8.0, I'm wondering if this is the right interface for the type. Maybe this would be better: user_linger { 'foo':
ensure => enabled,
} It makes the type ensurable and removes the implementation ( What do you think @bastelfreak, @mcanevet? |
From a user point of view I think both ways are. The implementation for your |
Given how many users/resources there may be on a given system, you may want to have a Hash interface that only creates one resource to prevent death by 10k resources. Probably future work, but something to keep in mind before this completely goes down the |
Yes, the core type was an option, too. That would require adding a new feature also. It is probably possible to provide this as a plugin with some monkey patching... but supporting that on the long run might not be fun... and does it make sense to implement linger for all OSes? |
Looking at the options a bit more, I would prefer the current implementation since it reduces system resources. Technically, you could implement both and make them conflict with each other but that may be too much work. |
@trevor-vaughan why does it reduce system resources? |
@raphink Because
|
Good point... so let's keep it the way it is then. I'll cut the release tomorrow I think. |
Example usage: