[systemd-devel] udev vs. nscd vs. /var automount
Łukasz Stelmach
l.stelmach at samsung.com
Thu Apr 7 13:54:32 UTC 2016
It was <2016-04-07 czw 15:52>, when Lennart Poettering wrote:
> On Wed, 06.04.16 11:15, Łukasz Stelmach (l.stelmach at samsung.com) wrote:
>> I've hit a problem caused by a mix of: automounting + glibc + udev + my
>> partition layout. Apparently it is impossible to make /var automountable
>> because udev (which needs to enumerate devices befor mounting them) is
>> trying to connect to /var/run/nscd/socket (that's actually glibc
>> code). This attempt does not fail because autofs tells there still is
>> hope that the path will appear soon but it won't because udev can't tell
>> the device to mount exists.
>>
>> I've checked glibc source and it still refers to /var/run/nscd/socket
>> rather than /run/nscd/socket. As far as I know there is no way to
>> disable nscd lookups.
>>
>> Any idead how to cope with it?
>
> Don't see any. Only option really is to fix glibc to not use /var/run
> anymore, but use /run instead. Consider filing a bug against glibc.
I am considering ;-) I talked on IRC that a patch implementing
compile-time configuration should be acceptable.
--
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 472 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20160407/99560763/attachment.sig>
More information about the systemd-devel
mailing list