creating and packaging the directory for the user could have been a nice aid; possibly putting a README (hoping sssd would only load *.conf files) with some starting points on how to configure it

Could the example be packaged as %doc, so that users have at least some reference ?

packaging "the" directory

Shipping empty directories in /etc, while not as bad as shipping files in /etc, is still a cosmetic nuisance as far as the container efforts go. You never if the admin resets/replaces /etc in some form or fashion, and so rpm would be racing with the admin in possibly reinstating the directory everytime (if it can — is readonly-/etc a thing yet?). So I think it is better to not any /etc files, regular or directory, with rpms.

Dominique Leuenberger (dimstar) - 7 months ago

reviewer

• Read-only /etc is not anything I heard about so far. Admins are supposed to configure their systems

• Even pam installs /etc/pam.d for the users to know where to put their config. The dir-structure being there helps the users guide to how to do the configuration

Could the example be packaged as %doc, so that users have at least some reference ?

Hm, yes. But also: man sssd.conf -> EXAMPLES. What do you think about that?

Dominique Leuenberger (dimstar) - 7 months ago

reviewer

basically anything giving the users some hints / starting points sounds like a good thing to offer

---

Dominique Leuenberger (dimstar) - 7 months ago

reviewer

One important thing (which the template sssd.conf just offered) is the fact that sssd.conf MUST be mode 0600 - or sssd refuses to start