| Message ID | 20230827164122.17735-2-sveyret@gmail.com |
|---|---|
| State | Accepted, archived |
| Commit | 1ca031b77546056ca1994469b0f2e93ea2018edf |
| Headers | show |
| Series | [meta-oe] volatile-binds: Allow creation of subdirectories | expand |
Hello, This patch and the next one ( https://lists.openembedded.org/g/openembedded-core/message/186843 ) have not been integrated yet. Have they been forgotten, should I do some modifications, or have they been definitly rejected ? Thanks.
diff --git a/meta/recipes-core/volatile-binds/files/volatile-binds.service.in b/meta/recipes-core/volatile-binds/files/volatile-binds.service.in index 52384c8264..5a0055bec3 100644 --- a/meta/recipes-core/volatile-binds/files/volatile-binds.service.in +++ b/meta/recipes-core/volatile-binds/files/volatile-binds.service.in @@ -3,7 +3,8 @@ Description=Bind mount volatile @where@ DefaultDependencies=no Before=local-fs.target RequiresMountsFor=@whatparent@ @whereparent@ -ConditionPathIsReadWrite=@whatparent@ +ConditionPathIsReadWrite=|@whatparent@ +ConditionPathExists=|!@whatparent@ ConditionPathExists=@where@ ConditionPathIsReadWrite=!@where@
The mount-copybind script will create the parent directory of the bind mount if it does not exist. But actually, if this is the case, the service will not even start because of the ConditionPathIsReadWrite. This patch adds a "or" condition to allow the service to start also if the parent directory of the bind mount does not exist. Signed-off-by: Stéphane Veyret <sveyret@gmail.com> --- .../volatile-binds/files/volatile-binds.service.in | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)