openrc/init.d/tmpfiles.setup.in

#!@SBINDIR@/openrc-run
# Copyright 1999-2012 Gentoo Foundation
# Released under the 2-clause BSD license.

description="set up tmpfiles.d entries"

depend()
{
	need localmount
}

start()
{
	ebegin "setting up tmpfiles.d entries"
	@LIBEXECDIR@/sh/tmpfiles.sh --exclude-prefix=/dev --create --remove \
		${tmpfiles_opts}
	eend $?
	return 0
}
Rename runscript to openrc-run This was requested by Debian, because the minicom software, which is available on Debian and other distros, has a binary named runscript. We are keeping a backward compatibility symlink for now, but this allows Debian or any other distro to safely remove the symlink. X-Gentoo-Bug: 494220 X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=494220 2013-12-22 02:21:11 +05:30			`#!@SBINDIR@/openrc-run`
tmpfiles.d init.d scripts Now that the tmpfiles.d code is more tested, actually call it from init.d. It assumes that /run is already available when it runs. Please note it runs TWICE. - During sysinit, ideally just after /dev/shm is created, but before udev has started. After udev is also acceptable, but not ideal. - During boot, ideally just after localmount has completed. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> 2012-09-27 04:12:37 +05:30			`# Copyright 1999-2012 Gentoo Foundation`
			`# Released under the 2-clause BSD license.`

Tmpfiles: create and delete entries once in the boot runlevel. Initially, we were creating tmpfiles entries in the sysinit runlevel and again in the boot runlevel. Systemd runs the --create and --remove options in one service called systemd-tmpfiles-setup after the local file systems are mounted. Now we have a service called tmpfiles.setup which emulates this. This also closes the bug mentioned below, since we were originally writing to files that were on read-only file systems and that were not available. Reported-by: <devurandom@gmx.net> X-Gentoo-Bug: 439012 X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=439012 2012-10-31 21:23:37 +05:30			`description="set up tmpfiles.d entries"`
tmpfiles.d init.d scripts Now that the tmpfiles.d code is more tested, actually call it from init.d. It assumes that /run is already available when it runs. Please note it runs TWICE. - During sysinit, ideally just after /dev/shm is created, but before udev has started. After udev is also acceptable, but not ideal. - During boot, ideally just after localmount has completed. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> 2012-09-27 04:12:37 +05:30
			`depend()`
			`{`
			`need localmount`
			`}`

			`start()`
			`{`
Tmpfiles: create and delete entries once in the boot runlevel. Initially, we were creating tmpfiles entries in the sysinit runlevel and again in the boot runlevel. Systemd runs the --create and --remove options in one service called systemd-tmpfiles-setup after the local file systems are mounted. Now we have a service called tmpfiles.setup which emulates this. This also closes the bug mentioned below, since we were originally writing to files that were on read-only file systems and that were not available. Reported-by: <devurandom@gmx.net> X-Gentoo-Bug: 439012 X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=439012 2012-10-31 21:23:37 +05:30			`ebegin "setting up tmpfiles.d entries"`
Introduce the tmpfiles.dev service This service handles setting up the tmpfiles entries for the /dev directory for Linux systems which needs to be run in the sysinit runlevel. 2013-07-25 23:03:03 +05:30			`@LIBEXECDIR@/sh/tmpfiles.sh --exclude-prefix=/dev --create --remove \`
			`${tmpfiles_opts}`
tmpfiles.d init.d scripts Now that the tmpfiles.d code is more tested, actually call it from init.d. It assumes that /run is already available when it runs. Please note it runs TWICE. - During sysinit, ideally just after /dev/shm is created, but before udev has started. After udev is also acceptable, but not ideal. - During boot, ideally just after localmount has completed. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> 2012-09-27 04:12:37 +05:30			`eend $?`
			`return 0`
			`}`