Bug 12797 - Init reports "No inittab.d directory" after clean baremetal install
Summary: Init reports "No inittab.d directory" after clean baremetal install
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: initscripts (show other bugs)
Version: 2
Hardware: x86_64 Linux
: - Unknown - Aesthetic Issue
Assignee: Adolf Belka
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-12 19:55 UTC by Nick Eads
Modified: 2022-04-27 21:54 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Eads 2022-03-12 19:55:06 UTC
Overview: Init logs multiple "No inittab.d directory found" messages in /var/log/messages and reflected in the log summary web page. This happens on boots of clean, baremetal installs of Cores 163 and 164.

Steps to reproduce:

1. Install a recent clean Core (tested with 163 and 164 specifically).
2. Check /var/log/messages and/or Init section of log summary when available.

Actual Results: Log contains "No inittab.d directory found" message(s).

Expected Results: No message(s) found in log regarding missing inittab.d directory.

Build Date & Hardware: IPFire 2.27 (x86_64) - Core Update 164

Additional Builds and Platforms: Also affects Core Update 163 and earlier (see Additional Information Section below).

Forum Thread: See community forum where this bug was reproduced by multiple users: https://community.ipfire.org/t/missing-inittab-d-directory/7416

Additional Information: In the thread, user bonnietwin states the following:

"I just had a search through the sysvinit changelog and in sysvinit-2.97 (Dec2020) a patch was added to sysvinit which allows init to load configuration data from files stored in /etc/inittab.d/ . This modification would have come in with Core Update 155."
Comment 1 Michael Tremer 2022-03-14 15:31:28 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.
Comment 2 Nick Eads 2022-03-14 15:35:54 UTC
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.
Comment 3 Adolf Belka 2022-03-14 16:03:55 UTC
Hi @Michael,
Yes, I will pick this up.
Comment 4 Adolf Belka 2022-03-17 21:30:01 UTC
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/
Comment 6 Adolf Belka 2022-04-04 20:03:33 UTC
Patch has been merged into next - CU167
Comment 7 Adolf Belka 2022-04-14 16:20:59 UTC
CU167 Testing has been released so the fix can be evaluated.
Comment 8 Adolf Belka 2022-04-14 16:21:19 UTC
Fix tested out with CU167 Testing.

The "No ininittab.d directory found" message is no longer being created.