Opened 2 years ago
Closed 2 years ago
#15756 closed defect (fixed)
Convert Unbound to use the upstream-provided systemd unit
| Reported by: | Douglas R. Reno | Owned by: | Douglas R. Reno |
|---|---|---|---|
| Priority: | normal | Milestone: | 11.1 |
| Component: | BOOK | Version: | systemd |
| Severity: | normal | Keywords: | |
| Cc: |
Description
There is an error in the systemd unit that we provide for Unbound that causes it to intermittently prevent systems from booting.
Scott Andrews in blfs-support suggested/provided a fix, but after looking upstream, I've discovered that Unbound now provides a systemd unit in the contrib folder, so let's use that instead.
Change History (4)
comment:1 by , 2 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 2 years ago
| Type: | enhancement → defect |
|---|
comment:3 by , 2 years ago
The systemd unit provided by Unbound causes systemctl to hang (but if you run systemctl status unbound from another terminal, it's started fine even though it's claimed that it's starting still). I believe the reason behind that is that the systemd unit is attempting to run unbound in a chroot.
I'm going to update the systemd unit that we provide with the proper After= clause (local-fs.target network-online.target)
comment:4 by , 2 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Marking as 'defect' instead of 'enhancement'