On 11/29/18 7:46 AM, Pavel Březina wrote:
> On 11/28/18 4:37 PM, Robert Marcano wrote:
>> On 11/28/18 11:20 AM, Ralf Corsepius wrote:
>>> On 11/28/18 3:45 PM, Florian Weimer wrote:
>>>> * Richard W. M. Jones:
>>>>
>>>>> Trying to track down a bug in IPP printing
>>>>> (
https://bugzilla.redhat.com/show_bug.cgi?id=1653276).
>>>>>
>>>>> We're down a rabbit hole where it seems that in Fedora 29
>>>>> /etc/nssswitch.conf ought to be a symlink. This machine has been
>>>>> upgraded from F28 and this is not the case. AFAIK I have never
>>>>> edited
>>>>> the file.
>>>>
>>>> /etc/nsswitch.conf is owned by glibc. It is not a symbolic link as we
>>>> ship it.
>>>>
>>>> If find out which packages replaces our configuration with a symbolic
>>>> link,
>>>
>>> It's authselect.
>>>
>>> # rpm -qV glibc
>>> ....L.... c /etc/nsswitch.conf
>>>
>>>
>>> # ls -l /etc/nsswitch.conf
>>> lrwxrwxrwx. 1 root root 29 Nov 18 04:58 /etc/nsswitch.conf ->
>>> /etc/authselect/nsswitch.conf
>>
>> My clean F29 installation had no such symbolic link, has to
>> "authselect select --force ..." to force the creation of the link.
>>
>> The non symlinked /etc/nsswitch.conf even had the header:
>>
>> # Do not modify this file manually.
>>
>> # If you want to make changes to nsswitch.conf please modify
>> # /etc/authselect/user-nsswitch.conf and run 'authselect
>> apply-changes'.
>>
>> So, was it generated at some point by authselect and not as symbolic
>> link?
>>
>> Note: Today I got new update for authselect (1.0.2-1.fc29)
>
> Authselect did not take over default nsswitch.conf (that comes from
> glibc) and pam settings (from pam). Installation of authselect package
> it self does not make any changes, you need to invoke the authselect
> command somehow -- anaconda invokes it automatically during
> installation without kickstart.
>
> If you see this comment in nsswitch.conf and yet nsswitch.conf is a
> file, not a symlink to /etc/authselect I suppose you are using some
> sort of snapshot?
>
The presence of the comments tell me that probably authselect was
properly called by anaconda as you say, but some other package decided
to modify nsswitch (The only external repository I have is VS Code).
Will try to test on a new VM reinstalling my current package list in
order to try to detect what or why.
It was probably systemd or nss-mdns. This is a known issue and I am in
touch with their maintainers to solve this. Also, see the other thread
"nsswitch.conf: list of module packages that enables themselves".
>
>
>
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org