add bus property for socket units showing the used selinux label of the socket
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c, linux
- Domain
- operating-systems
Research direction
Start by locating the socket-unit show or status output and the code that determines the SELinux context from the service's ExecStart path. Done means the socket unit exposes the path used for context determination, making failed socket startup easier to troubleshoot.
Written by the indexing model from the issue text.
Description
Currently, systemd starts a socket using the sexlinux context of the corresponding service's ExecStart path. This behavior is opaque to an administrator who is troubleshooting a failed socket unit startup. We should consider displaying the path used for context determination in the show or status output of the socket unit.
- Dominant language
- C
- Stars
- 16.7k
- Forks
- 4.7k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 140
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from systemd/systemd
-
bug 🐛 documentation release-critical
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
systemd-analyze plot: Activation times are wrong in tooltip if the decimal part starts with zero Openbug 🐛
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug 🐛 sd-boot/sd-stub/bootctl
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
journal RFE 🎁
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
bug 🐛 ssh-generator
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Similar issues
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Shipwright#7229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
riscv-software-src/riscv-isa-sim#2435 · 1 comment ·
-
bug Self Built Image SNAPSHOT Supported Device target/ramips
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100