freebsd-src/libexec/rc/rc.d/hostname
Alexander Leidinger f99f0ee14e rc.d: add a service jails config to all base system services
This gives more permissions to services (e.g. network access to
services which require this) when they are started as an automatic
service jail.

The sshd patch is important for the sshd-related functionality as
described in the man-page in the service jails part.

The location of the added env vars is supposed to allow overriding them
in rc.conf, and to hard-disable the use of svcj for some parts where it
doesn't make sense or will not work.

Only a subset of all of the services are fully tested (I'm running this
since more than a year with various services started as service jails).
The untested parts should be most of the time ok, in some edge-cases
more permissions are needed inside the service jail.
Differential Revision:	https://reviews.freebsd.org/D40371
2024-05-22 15:41:49 +02:00

85 lines
2.6 KiB
Bash
Executable file

#!/bin/sh
#
# Copyright (c) 2003 The FreeBSD Project. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in the
# documentation and/or other materials provided with the distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
# SUCH DAMAGE.
#
#
# PROVIDE: hostname
# REQUIRE: FILESYSTEMS
# BEFORE: netif
. /etc/rc.subr
. /etc/network.subr
name="hostname"
desc="Set the system\'s hostname"
start_cmd="hostname_start"
stop_cmd=":"
hostname_start()
{
# If we are not inside a jail, set the host name.
# If we are inside a jail, set the host name if it is permitted.
#
if [ `$SYSCTL_N security.jail.jailed` -eq 1 ]; then
if [ `$SYSCTL_N security.jail.set_hostname_allowed` -eq 0 ]; then
return
fi
else
# If we're not in a jail and rc.conf doesn't specify a
# hostname, see if we can get one from kenv.
#
if [ -z "${hostname}" -a \
-n "`/bin/kenv dhcp.host-name 2> /dev/null`" ]; then
hostname=`/bin/kenv dhcp.host-name`
fi
fi
# Have we got a hostname yet?
#
if [ -z "${hostname}" ]; then
# Null hostname is probably OK if DHCP is in use,
# or when hostname is already set (common for jails).
#
if [ -z "`list_net_interfaces dhcp`" -a \
-z "`/bin/hostname`" ]; then
warn "\$hostname is not set -- see rc.conf(5)."
fi
return
fi
# All right, it is safe to invoke hostname(1) now.
#
startmsg -n "Setting hostname: ${hostname}"
/bin/hostname "${hostname}"
startmsg '.'
}
load_rc_config $name
# doesn't make sense to run in a svcj: config setting
hostname_svcj="NO"
run_rc_command "$1"