Project

General

Profile

Actions
Copy link

Task #5304

closed

Change default Unix socket path to /run/nfd/nfd.sock

Added by Junxiao Shi almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Davide Pesavento
Category:
Faces
Target version:
24.07
Start date:
Due date:
% Done:

100%

Estimated time:
3.00 h
Tags:
approved docker systemd

Description

Presently, NFD creates the Unix socket at /run/nfd.sock.
This causes difficulty in NFD Docker packaging: either the container must mount /run in read-write mode which gives the container too much privilege, or the client.conf must be edited to point to a different socket path.

This issue is to change the default Unix socket path path to /run/nfd/nfd.sock, without any backwards compatibility.
NFD must create the enclosing directory if it does not exist.

Actions
Copy link
 #1

Updated by Junxiao Shi almost 2 years ago

  • Tags set to approved

20231208 NFD call has approved this issue.

Actions
Copy link
 #2

Updated by Davide Pesavento almost 2 years ago

  • Tags changed from approved to approved, docker, systemd
  • Subject changed from Change Unix socket path to /run/nfd/nfd.sock to Change default Unix socket path to /run/nfd/nfd.sock

FWIW, moving the socket file to a subdir will also enable running NFD as a systemd service without full root privileges.

Actions
Copy link
 #3

Updated by Davide Pesavento almost 2 years ago

  • Tracker changed from Feature to Task
  • Status changed from New to In Progress
  • Assignee changed from Varun Patil to Davide Pesavento
  • % Done changed from 0 to 50
Actions
Copy link
 #5

Updated by Davide Pesavento almost 2 years ago

  • Status changed from Code review to Closed
  • % Done changed from 50 to 100
Actions
Copy link
 #7

Updated by Junxiao Shi almost 2 years ago

NDNts has supported the new socket path, with limited backwards compatibility, in this commit:
https://github.com/yoursunny/NDNts/commit/0b748bf7d67580d3a07ed2cdd3a9590b5fdacdf1

Mini-NDN is possibly broken according to this complaint:
https://www.lists.cs.ucla.edu/pipermail/nfd-dev/2024-January/004555.html

ppa-packaging has a copy of nfd.conf with old socket path.
This affects NFD-nightly: nfdc would attempt to connect to new socket path, while nfd listens on old socket path.

Actions
Copy link

Also available in: Atom PDF