Bug 2342274

Summary: Please change unbound service type into "notify"
Product: [Fedora] Fedora Reporter: Tomas Korbar <tkorbar>
Component: unboundAssignee: Paul Wouters <paul.wouters>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: paul.wouters, pemensik, pj.pandit
Target Milestone: ---Keywords: RFE
Target Release: ---Flags: tkorbar: mirror+
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-18 12:30:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomas Korbar 2025-01-27 15:38:41 UTC 
Hi,
currently unbound service type is "simple" that means the unit is considered started when systemd's fork call succeeds. This is problematic as if you want to start another service only after unbound is running, then you have to poll. If unbound was "notify" service then the synchronization would work as expected.

Reproducible: Always

Steps to Reproduce:
You can try to create service that "Wants=unbound.service" but that would not work always as there is naturally a race. So simply switch unbound service to notify, build it with libsystemd support or otherwise write to appropriate socket and verify that systemctl start unbound.service works, as service without stating "READY=1" should not be able to start.
Actual Results:  
unbound.service is "simple" service

Expected Results:  
unbound.service is "notify" service
Comment 1 Tomas Korbar 2025-02-18 12:30:45 UTC 
Fixed in rawhide.