Skip to content

Conversation

@OlivierB
Copy link

The /run/network directory is used by ifupdown2 for locks and state files.
This directory is created at service startup (networking). But if we want, for
example, to use ifquery before network start, it fails.
We can ensure that /run/network directory is always present with systemd-tmpfiles.

We could do it with systemd RuntimeDirectory in the networking service, but it
does not seem to be the right method with the standalone mode.

Preliminary work : Debhelper update.

Olivier BLIN added 4 commits November 10, 2023 20:09
The /run/network directory is used by ifupdown2 for locks and state files.
This directory is created at service startup (networking). But if we want, for
example, to use ifquery before network start, it fails.
We can ensure that /run/network directory is always present with systemd-tmpfiles.

We could do it with systemd RuntimeDirectory in the networking service, but it
does not seem to be the right method with the standalone mode.

Like /run/network, we can move /etc/network/run symlink creation in ifupdown2 tmpfiles
and /etc/network/run directory symlink.

We no longer need to worry about the existence of this directory.
The system handles the creation.
@OlivierB
Copy link
Author

Hello,

I have split system configuration and codebase modification for the /run/network directory. The last commit on the codebase update is a very bad idea if ifupdown2 is built for non Debian system.

I wait for your decision to known if we can keep it.

@OlivierB OlivierB changed the title Ensure ifupdown2 runtime directory always exists Ensure ifupdown2 runtime directory always exists (and debhelper 13 update) Nov 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant