Re: Manual intervention required: broken /etc/nsswitch.conf and /etc/resolv.conf for F33 early adopters

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Fri, Sep 11, 2020 at 10:21 am, Kamil Paral <kparal@xxxxxxxxxx> wrote:
I did edit /etc/nsswitch.conf manually, because obviously I needed a working system :) The confusing part here is that the error message claims that **/etc/authselect/nsswitch.conf** has unexpected content. So this doesn't seem to be related to /etc/nsswitch.conf having been edited by hand. Is it?

I think it's probably related. It's unexpected for it to not match your /etc/nsswitch.conf.

If it is, what is the proper way to revert back to upstream defaults in this case? Should I append "--force" to the command? (I don't want to destroy my system, that's why I'm not simply trying it. All of this seems awfully complex and fragile).

Yes, use --force. That tells authselect that it is OK to overwrite your manual configuration. Otherwise, authselect is careful to not overwrite files that have been edited manually.

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux