GNU bug report logs - #48751
[PATCH 0/1] Create parent directory for laminar unix socket

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Arun Isaac <arunisaac <at> systemreboot.net>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#48751: closed ([PATCH 0/1] Create parent directory for
 laminar unix socket)
Date: Thu, 10 Jun 2021 05:01:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Thu, 10 Jun 2021 10:30:12 +0530
with message-id <87eedajov7.fsf <at> systemreboot.net>
and subject line Re: [bug#48751] [PATCH] services: laminar: Create parent directory for unix socket.
has caused the debbugs.gnu.org bug report #48751,
regarding [PATCH 0/1] Create parent directory for laminar unix socket
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
48751: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=48751
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Arun Isaac <arunisaac <at> systemreboot.net>
To: guix-patches <at> gnu.org
Cc: Arun Isaac <arunisaac <at> systemreboot.net>
Subject: [PATCH 0/1] Create parent directory for laminar unix socket
Date: Mon, 31 May 2021 01:29:52 +0530

If laminard is configured to listen on a unix socket, it should create the
parent directory of the unix socket with appropriate permissions. Currently,
no parent directory is created and the service fails to start.

Arun Isaac (1):
  services: laminar: Create parent directory for unix socket.

 gnu/services/ci.scm | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

-- 
2.31.0

[Message part 3 (message/rfc822, inline)]

From: Arun Isaac <arunisaac <at> systemreboot.net>
To: Christopher Baines <mail <at> cbaines.net>
Cc: 48751-done <at> debbugs.gnu.org
Subject: Re: [bug#48751] [PATCH] services: laminar: Create parent directory
 for unix socket.
Date: Thu, 10 Jun 2021 10:30:12 +0530

[Message part 4 (text/plain, inline)]

Hi Chris,

> This looks good to me.

Pushed to master, thanks for the review!

> I don't think I've played around too much with different bind options,
> so I haven't come across this issue.

One problem still remains even after this patch. If the laminar web UI
is behind an nginx reverse proxy, the nginx user needs to have
read/write permissions to the unix socket. For this, it should be a
member of the laminar group. But, short of modifying the nginx service,
I don't know of any way to achieve this. Something more composable would
be nice. The nginx service being aware of laminar doesn't sound
right. Any ideas?

Regards,
Arun

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.