Re: [devel] [PATCH hasher-priv v1 1/3] Makefile

[Arseny Maslennikov <ar@cs.msu.ru>]

[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]

On Fri, Sep 18, 2020 at 02:33:12PM +0300, Dmitry V. Levin wrote:
> On Thu, Sep 17, 2020 at 04:12:36PM +0300, Arseny Maslennikov wrote:
> > On Fri, Dec 13, 2019 at 12:42:03PM +0100, Alex Gladkov wrote:
> [...]
> > > @@ -21,6 +21,7 @@ man5dir = $(mandir)/man5
> > >  man8dir = $(mandir)/man8
> > >  configdir = $(sysconfdir)/$(PROJECT)
> > >  helperdir = $(libexecdir)/$(PROJECT)
> > > +socketdir = /var/run
> > 
> > Why /var/run and not /run, especially in a new project?
> 
> It's the same thing nowadays, isn't it?

Short answer: That's why I asked the question.

Long answer: Depends on what you mean by "thing".

It is true that these two paths point to the same place now, but
/var/run is only kept for compatibility with software that expects this
path to be available, so we, the packagers, don't have to patch all of
it now.

The mountpoints, however, have an obvious but important difference:
/var/run requires /var to be mounted first to work correctly, and /run
does not — so the latter path is more simple and thus preferable, and
the former path was a mistake.

> 
> > Even further, I would suggest that we store the socket in
> > /run/hasher-priv or something, setgid hashman, with 0710 rights. The
> > major service managers can create the directory on startup for us:
> > there's mkdir(1), there's RuntimeDirectory= and RuntimeDirectoryMode=.
> 
> I distinctly remember we discussed this the last autumn or winter.

The discussion probably went over my head then, or was private.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]