Summary: | Init reports "No inittab.d directory" after clean baremetal install | ||
---|---|---|---|
Product: | IPFire | Reporter: | Nick Eads <eadsnr> |
Component: | initscripts | Assignee: | Adolf Belka <adolf.belka> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | Aesthetic Issue | ||
Priority: | - Unknown - | CC: | michael.tremer, peter.mueller |
Version: | 2 | ||
Hardware: | x86_64 | ||
OS: | Linux |
Description
Nick Eads
2022-03-12 19:55:06 UTC
Thanks for your report. @Adolf: Would you like to grab this one? We just need to create the directory and since we are not using it, we won't need to do anything more. I should have added that I did test manually adding the directory and that it does indeed work to prevent future instances of the message from being logged. Hi @Michael, Yes, I will pick this up. Patch to fix this has been submitted to the dev mailing list and to patchwork. https://patchwork.ipfire.org/project/ipfire/patch/20220317212715.3543142-1-adolf.belka@ipfire.org/ Patch has been merged into next - CU167 CU167 Testing has been released so the fix can be evaluated. Fix tested out with CU167 Testing. The "No ininittab.d directory found" message is no longer being created. |