Hearns, John said the following on 04/29/2013 12:42 PM:
However, the original poster asked for 'LDAP like' change management - I rather thought she might like to look at Puppet. Where is this "Change management"? I read it as a means of having central administration. "Change management" in a database would mean Git or something like that.
Lynn works with LDAP as a central database so she would ask in terms of that. She might as well as "Why aren't the CRON tables implemented in LDAP just like all the other things we see in. for example, /etc/nsswitch.conf?" Hi everyone. Thanks for your interest. Maybe I should explain what I mean by LDAP
On 29/04/13 19:09, Anton Aylward wrote: like. A good example is when I add a user to a group. I don't have to go around altering /etc/group on all the clients. I just do it once in LDAP and let sssd pull it out next the next time the user logs in. On any client. That supposes I already have the sss target for group in nsswitch.conf. If I haven't, I'm in the situation I'm in now. I don't have the script I need in cron.hourly on the clients so I've got to go around them all or use one of the methods you have very kindly suggested. But e.g. to setup ssh, I'd still have to go to each client and do something as root. This sort of situation doesn't occur often enough to justify the time I'd need to do that. Summary. I want to sit at one computer and copy a file to /etc/cron.hourly on all the clients. Without physically walking to each client, I don't think I can do that. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org