On Fri, 2020-02-07 at 11:36 +0100, Thorsten Kukuk wrote:
On Fri, Feb 07, Michael Ströder wrote:
On 2/7/20 8:27 AM, Thorsten Kukuk wrote:
On Fri, Feb 07, Roger Oberholtzer wrote:
If there was a program that could be told a service and add it if it does not exist, then what you say might be true. But most installers like ours check if a service is defined, and if not, add it to the services file. So it needs to know the location. Is there a user command that tells the name of this file?
So your installer is already broken today if the customer is using LDAP or NIS?
I'm in the LDAP world for 20+ years now. I don't know any deployment where services map is delivered via LDAP (even though RFC 2307 defines the schema and nss_ldap and nss-pam-ldap aka nslcd support services map). It would also be pretty stupid to do that.
Depends how you distribute your software. If you install the software on every single machine: ok. If you, like we did at university, distribute the software via NFS, you don't want to mess around with /etc/services on every single of the 5000 machines, you want to add the necessary entries for the software in one central place.
Indeed, I've been in the LDAP world as long as Michael, and had a former life a sysadmin in academia. Thorsten's use case rings true to exactly how we used to deploy things in my previous job. Works very well when you have a multi-thousand workstation network being consumed by multi-tens-of-thousands LDAP tree with a churn rate of ~15,000 users added/removed each academic year. Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org