freebsd-nq/etc/rc.d/ddb

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

# PROVIDE: ddb
# REQUIRE: dumpon
# BEFORE: disks
# KEYWORD: nojail

. /etc/rc.subr

name="ddb"
desc="DDB kernel debugger"
rcvar="ddb_enable"
command="/sbin/${name}"
start_precmd="ddb_prestart"
start_cmd="ddb_start"
stop_cmd=":"

ddb_prestart()
{
	# Silently exit if ddb is not enabled
	if [ -z "`sysctl -Nq debug.ddb.scripting.scripts`" ]; then
		return 1
	fi
}

ddb_start()
{
	${command} ${command_args}
}

load_rc_config $name

required_files="${ddb_config}"
command_args="${ddb_config}"

run_rc_command "$1"
Use the new command file feature of ddb(8) to support setting ddb(4) scripts at boot. This is currently disabled by default. /etc/ddb.conf contains some potentially reasonable default scripts. PR: conf/119995 Submitted by: Scot Hetzel <swhetzel at gmail dot com> (Earlier version) X-MFC after: textdumps 2008-03-05 18:32:58 +00:00			`#!/bin/sh`
			`#`
			`# $FreeBSD$`
			`#`

			`# PROVIDE: ddb`
			`# REQUIRE: dumpon`
This change does the following for the scripts that run up through FILESYSTEMS (the default early_late_divider): 1. Move sysctl to run first 2. Move as many BEFOREs to REQUIREs as possible. 3. Minor effect, move hostid_save from right before mdconfig to right after. A lot of the early scripts make use of sysctl one way or another so running this first makes a lot of sense given that system-critical values are often placed in sysctl.conf. My original purpose for working on this was that while doing some debugging on other stuff I noticed that the order of execution was different in the first pass through the early scripts and the second. In practice that doesn't matter because the scripts are not executed the second time. However this _can_ result in problems if the difference in the rcorder moves a script from the late section to the early section in the second pass (which would mean the script would not get executed). So, I wanted to make the order of execution of the scripts in the early section more deterministic. In the course of debugging the ordering problems I noticed that moving the BEFOREs to REQUIREs prevented the changes in order from the first pass to the second pass without having to make any substantial changes. (Of course it's no secret that I think BEFORE should be avoided as much as possible, but this is a good example of why.) Reviewed by: silence on freebsd-rc@ MFC after: 8.1-RELEASE 2010-05-19 19:03:19 +00:00			`# BEFORE: disks`
Use the new command file feature of ddb(8) to support setting ddb(4) scripts at boot. This is currently disabled by default. /etc/ddb.conf contains some potentially reasonable default scripts. PR: conf/119995 Submitted by: Scot Hetzel <swhetzel at gmail dot com> (Earlier version) X-MFC after: textdumps 2008-03-05 18:32:58 +00:00			`# KEYWORD: nojail`

			`. /etc/rc.subr`

			`name="ddb"`
- Add descriptions to most of the rc scripts. Those are mostly taken from their daemon's manpage and probably improved. - Consistently use "filesystem" not "file system". Approved by: bapt, brueffer Differential Revision: D452 2016-04-23 16:10:54 +00:00			`desc="DDB kernel debugger"`
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="ddb_enable"`
Use the new command file feature of ddb(8) to support setting ddb(4) scripts at boot. This is currently disabled by default. /etc/ddb.conf contains some potentially reasonable default scripts. PR: conf/119995 Submitted by: Scot Hetzel <swhetzel at gmail dot com> (Earlier version) X-MFC after: textdumps 2008-03-05 18:32:58 +00:00			`command="/sbin/${name}"`
			`start_precmd="ddb_prestart"`
Fix ddb rc script r288291 added a call to limits(1), which isn't available before partitions are mounted. This broke the ddb rc script, which does not provide its own start_cmd. Alleviate the situation here by providing a start_cmd. We still have other problems with diskless setups that need to be considered, but this is a start. PR: 206291 Submitted by: cy Discussed with: rgrimes MFC after: 3 days 2018-04-19 15:02:53 +00:00			`start_cmd="ddb_start"`
Use the new command file feature of ddb(8) to support setting ddb(4) scripts at boot. This is currently disabled by default. /etc/ddb.conf contains some potentially reasonable default scripts. PR: conf/119995 Submitted by: Scot Hetzel <swhetzel at gmail dot com> (Earlier version) X-MFC after: textdumps 2008-03-05 18:32:58 +00:00			`stop_cmd=":"`

			`ddb_prestart()`
			`{`
			`# Silently exit if ddb is not enabled`
			if [ -z "`sysctl -Nq debug.ddb.scripting.scripts`" ]; then
			`return 1`
			`fi`
			`}`

Fix ddb rc script r288291 added a call to limits(1), which isn't available before partitions are mounted. This broke the ddb rc script, which does not provide its own start_cmd. Alleviate the situation here by providing a start_cmd. We still have other problems with diskless setups that need to be considered, but this is a start. PR: 206291 Submitted by: cy Discussed with: rgrimes MFC after: 3 days 2018-04-19 15:02:53 +00:00			`ddb_start()`
			`{`
			`${command} ${command_args}`
			`}`

Use the new command file feature of ddb(8) to support setting ddb(4) scripts at boot. This is currently disabled by default. /etc/ddb.conf contains some potentially reasonable default scripts. PR: conf/119995 Submitted by: Scot Hetzel <swhetzel at gmail dot com> (Earlier version) X-MFC after: textdumps 2008-03-05 18:32:58 +00:00			`load_rc_config $name`

			`required_files="${ddb_config}"`
			`command_args="${ddb_config}"`

			`run_rc_command "$1"`