freebsd/etc/rc.d/ftpd

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

# PROVIDE: ftpd
# REQUIRE: LOGIN FILESYSTEMS
# KEYWORD: shutdown

. /etc/rc.subr

name="ftpd"
rcvar="ftpd_enable"
command="/usr/libexec/${name}"
pidfile="/var/run/${name}.pid"
start_precmd=ftpd_prestart

ftpd_prestart()
{
	rc_flags="-D ${rc_flags}"
	return 0
}

load_rc_config $name
run_rc_command "$1"
Add an rc.d script for stand-alone ftpd. Document the script's controls on the rc.conf(5) manpage and touch its Dd. PR: conf/90893 MFC after: 5 days 2006-01-21 18:08:16 +00:00			`#!/bin/sh`
			`#`
			`# $FreeBSD$`
			`#`

			`# PROVIDE: ftpd`
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: LOGIN FILESYSTEMS`
Add the shutdown KEYWORD to those scripts that start persistent services to allow them to do a "clean" shutdown. I purposely avoided making changes to network-related stuff since the system shutting down is pretty conclusive, and there may be complicated dependencies on the network that I would rather not try to unravel. I also skipped kerberos-related stuff for the reasons above, and because I have no way to test it. 2008-07-16 19:50:29 +00:00			`# KEYWORD: shutdown`
Add an rc.d script for stand-alone ftpd. Document the script's controls on the rc.conf(5) manpage and touch its Dd. PR: conf/90893 MFC after: 5 days 2006-01-21 18:08:16 +00:00
			`. /etc/rc.subr`

			`name="ftpd"`
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="ftpd_enable"`
Add an rc.d script for stand-alone ftpd. Document the script's controls on the rc.conf(5) manpage and touch its Dd. PR: conf/90893 MFC after: 5 days 2006-01-21 18:08:16 +00:00			`command="/usr/libexec/${name}"`
			`pidfile="/var/run/${name}.pid"`
			`start_precmd=ftpd_prestart`

			`ftpd_prestart()`
			`{`
			`rc_flags="-D ${rc_flags}"`
			`return 0`
			`}`

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