This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: configuring /var/run with newer autoconf


On 04/11/2016 09:20 AM, Åukasz Stelmach wrote:
It was <2016-04-08 piÄ 14:31>, when Florian Weimer wrote:
On 04/08/2016 09:52 AM, Åukasz Stelmach wrote:

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.

Why?  It may need changes to autofs, so that it can produce the
required symbolic link, at an early stage of operation.

autofs works as expected, it does not provide any contents itself, instead it
intercepts all requests and put them on hold until the actual filesystem
is mounted. I wouldn't expect anything else.

For generating the symlinks in /var, I would expect to provide them.

Are you trying to automount /var itself, or is /var a directory monitored by the automounter?

I'd say the case we are discussing is an extremely rare corner case for
autofs and I'd rather expect requirement for autoconf 2.70 be accepted
in libc (-; before any kernel developer accepts a patch for autofs.

It's not just autoconf (which, as far as I understand it, is not released at this point). The pathname is part of the ABI, so we can't really change it for existing architectures.

Florian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]