Re: configuring /var/run with newer autoconf

[Åukasz Stelmach <l dot stelmach at samsung dot com>]

It was <2016-04-07 czw 19:51>, when Mike Frysinger wrote:
> On 07 Apr 2016 16:49, Åukasz Stelmach wrote:
>> TL;DR Is there a chance a patch requiring autconf 2.70 is going to be
>>       accepted?
>> 
>> I found myself in trouble because of a deadlock during boot (on
>> Linux). In short: the deadlock happens if I want to make /var
>> automountable because.
>> 
>> a) systemd controls controls automounts.
>> 
>> b) To mount a file-system systemd needs to know about the underlying
>>    block device.
>> 
>> c) udev tells systemd about devices available.
>> 
>> d) When udev starts it tries to make some queries via NSS which means
>>    connecting to nscd (/var/run/nscd/socket, hardcoded in nscd-client.h)
>> 
>> Effect: I can't configure /var to be automounted.
>> 
>> Solutions:
>> 
>> a) Compile glibc without nscd support. This works for me, now.
>> 
>> b) Make the path configurable so Linux systems, especially those
>>    controlled by systemd which requires /var/run to be a symlink
>>    pointing to /run which is mounted by systemd as tmpfs, can use /run
>>    instead of /var/run.
>
> b) has been discussed here in the past and declined:
> 	https://sourceware.org/ml/libc-alpha/2015-03/msg00828.html

I see.

> but you also have another option and what most people have been doing:
> c) symlink /var/run to /run

This does not help to avoid deadlocks at all.

-- 
Åukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

Attachment: signature.asc
Description: PGP signature