freebsd/etc/rc.d/dmesg

#!/bin/sh
#
# $FreeBSD$
#

# PROVIDE: dmesg
# REQUIRE: mountcritremote FILESYSTEMS
# BEFORE:  DAEMON
# KEYWORD: nojail

. /etc/rc.subr

name="dmesg"
rcvar="dmesg_enable"
dmesg_file="/var/run/dmesg.boot"
start_cmd="do_dmesg"
stop_cmd=":"

do_dmesg()
{
	rm -f ${dmesg_file}
	( umask 022 ; /sbin/dmesg $rc_flags > ${dmesg_file} )
}

load_rc_config $name
run_rc_command "$1"
Import the NetBSD 1.5 RC system. Note that `rc' and `rc.shutdown' could not be imported because we already have files with those names. 2001-06-16 07:16:14 +00:00			`#!/bin/sh`
			`#`
Merge in all the changes that Mike Makonnen has been maintaining for a while. This is only the script pieces, the glue for the build comes next. Submitted by: Mike Makonnen <makonnen@pacbell.net> Reviewed by: silence on -current and -hackers Prodded by: rwatson 2002-06-13 22:14:37 +00:00			`# $FreeBSD$`
Import the NetBSD 1.5 RC system. Note that `rc' and `rc.shutdown' could not be imported because we already have files with those names. 2001-06-16 07:16:14 +00:00			`#`

			`# PROVIDE: dmesg`
Simply things so that "#REQUIRE: FILESYSTEMS" means the file systems are fully "ready to go". 'FILESYSTEMS' states: "This is a dummy dependency, for services which require file systems to be mounted before starting." However, we have 'var' which is was run after 'FILESYSTEMS' and can mount /var if it already isn't mounted. Furthermore, several scripts cannot use /var until 'cleanvar' has done its thing. Thus "FILESYSTEMS" hasn't really meant all critical file systems are fully usable. 2012-09-11 05:04:59 +00:00			`# REQUIRE: mountcritremote FILESYSTEMS`
Merge in all the changes that Mike Makonnen has been maintaining for a while. This is only the script pieces, the glue for the build comes next. Submitted by: Mike Makonnen <makonnen@pacbell.net> Reviewed by: silence on -current and -hackers Prodded by: rwatson 2002-06-13 22:14:37 +00:00			`# BEFORE: DAEMON`
Remove a meaningless KEYWORD 2007-12-08 22:40:31 +00:00			`# KEYWORD: nojail`
Import the NetBSD 1.5 RC system. Note that `rc' and `rc.shutdown' could not be imported because we already have files with those names. 2001-06-16 07:16:14 +00:00
			`. /etc/rc.subr`

			`name="dmesg"`
Prepare for the removal of set_rcvar() by changing the rcvar= assignments to the literal values it would have returned. The concept of set_rcvar() was nice in theory, but the forks it creates are a drag on the startup process, which is especially noticeable on slower systems, such as embedded ones. During the discussion on freebsd-rc@ a preference was expressed for using ${name}_enable instead of the literal values. However the code portability concept doesn't really apply since there are so many other places where the literal name has to be searched for and replaced. Also, using the literal value is also a tiny bit faster than dereferencing the variables, and every little bit helps. 2012-01-14 02:18:41 +00:00			`rcvar="dmesg_enable"`
Merge in all the changes that Mike Makonnen has been maintaining for a while. This is only the script pieces, the glue for the build comes next. Submitted by: Mike Makonnen <makonnen@pacbell.net> Reviewed by: silence on -current and -hackers Prodded by: rwatson 2002-06-13 22:14:37 +00:00			`dmesg_file="/var/run/dmesg.boot"`
Import the NetBSD 1.5 RC system. Note that `rc' and `rc.shutdown' could not be imported because we already have files with those names. 2001-06-16 07:16:14 +00:00			`start_cmd="do_dmesg"`
			`stop_cmd=":"`

			`do_dmesg()`
			`{`
Merge in all the changes that Mike Makonnen has been maintaining for a while. This is only the script pieces, the glue for the build comes next. Submitted by: Mike Makonnen <makonnen@pacbell.net> Reviewed by: silence on -current and -hackers Prodded by: rwatson 2002-06-13 22:14:37 +00:00			`rm -f ${dmesg_file}`
			`( umask 022 ; /sbin/dmesg $rc_flags > ${dmesg_file} )`
Import the NetBSD 1.5 RC system. Note that `rc' and `rc.shutdown' could not be imported because we already have files with those names. 2001-06-16 07:16:14 +00:00			`}`

			`load_rc_config $name`
			`run_rc_command "$1"`