generic-poky/meta/recipes-core/volatile-binds/files/volatile-binds.service.in

[Unit]
Description=Bind mount volatile @where@
DefaultDependencies=false
Before=local-fs.target
RequiresMountsFor=@whatparent@ @whereparent@
ConditionPathIsReadWrite=@whatparent@
ConditionPathExists=@where@
ConditionPathIsReadWrite=!@where@

[Service]
Type=oneshot
RemainAfterExit=Yes
StandardOutput=syslog
TimeoutSec=0
ExecStart=/sbin/mount-copybind @what@ @where@
ExecStop=/sbin/umount @where@

[Install]
WantedBy=local-fs.target
volatile-binds: add recipe This recipe is designed to play a key role in a read-only rootfs of systemd based systems. It generates service files from a template, volatile-binds.service.in and the VOLATILE_BINDS variable. By default, VOLATILE_BINDS takes the value of "/var/volatile/lib /var/lib\n", which leads to the generation of volatile-var-lib.service file. This file doesn't have any effect in a read-write system, as it has "ConditionPathIsReadWrite = !/var/lib" in the [Unit] section. In other words, this file only has effect in a read-only rootfs. (From OE-Core rev: ed7d30dc0cdb6d6c56c50ac7a3440c4ed0ee70d3) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2014-07-23 09:40:12 +00:00			`[Unit]`
			`Description=Bind mount volatile @where@`
			`DefaultDependencies=false`
			`Before=local-fs.target`
			`RequiresMountsFor=@whatparent@ @whereparent@`
			`ConditionPathIsReadWrite=@whatparent@`
			`ConditionPathExists=@where@`
			`ConditionPathIsReadWrite=!@where@`

			`[Service]`
			`Type=oneshot`
			`RemainAfterExit=Yes`
			`StandardOutput=syslog`
			`TimeoutSec=0`
			`ExecStart=/sbin/mount-copybind @what@ @where@`
			`ExecStop=/sbin/umount @where@`

			`[Install]`
			`WantedBy=local-fs.target`