[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAF9ehCVKdT8-v6-gZy=tbX9w0pVT3M8YBdAcnXySsxEHUcUUDg@mail.gmail.com>
Date: Mon, 24 Oct 2022 15:07:53 -0500
From: Joel Sherrill <joel@...ms.org>
To: libc-coord@...ts.openwall.com
Subject: Re: Per-thread file system attributes
On Mon, Oct 24, 2022, 2:55 PM Rich Felker <dalias@...c.org> wrote:
> On Mon, Oct 24, 2022 at 06:41:51PM +0200, Florian Weimer wrote:
> > Some userspace file servers (e.g. Samba) want to change the current
> > directory (or chroot or umask) on individual threads, rather than
> > affecting the entire process. In some cases, this can avoid a userspace
> > emulation of kernel pathname resolution.
>
> Isn't this what the *at() functions were for? Why do we need a second
> solution to the same problem?
>
On RTEMS, the similar capability includes default file mask, chroot,
effective and actual user and group id, and more.
But you are right, the at* methods handle the cwd part of this. If a
program uses them.
--joel
> Rich
>
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
