emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#48751: closed ([PATCH 0/1] Create parent directory for laminar unix


From: GNU bug Tracking System
Subject: bug#48751: closed ([PATCH 0/1] Create parent directory for laminar unix socket)
Date: Thu, 10 Jun 2021 05:01:02 +0000

Your message dated Thu, 10 Jun 2021 10:30:12 +0530
with message-id <87eedajov7.fsf@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@gnu.org.)


-- 
48751: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=48751
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- 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




--- End Message ---
--- Begin Message --- Subject: Re: [bug#48751] [PATCH] services: laminar: Create parent directory for unix socket. Date: Thu, 10 Jun 2021 10:30:12 +0530
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

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]