summaryrefslogtreecommitdiffstats
path: root/etc
Commit message (Collapse)AuthorAgeFilesLines
* Don't bogusly depend on dhclient. It's now run either bybrooks2005-12-031-1/+1
| | | | /etc/rc.d/netif or from devd rather than by the startup scripts.
* "-o rw" is invalid and undocumented mount option thatru2005-12-021-1/+1
| | | | | | | | | | | | | | | | | is only present for fstab(5) compatibility, and is otherwise ignored by mount(8) (not passed to mount_* programs, and not passed to nmount(2)). "-u -o rw" worked with an old mount(8) with mount_ufs.c because "-o rw" was stripped and simple "-u" caused an update of UFS from read-only to read-write, due to inability of mount(2) to track changes in options (MNT_RDONLY is either set or not). "-u" no longer causes the transition from RO to RW, now that mount(8) was converted to use nmount(2), so an explicit change to RW is required. Keep up with this change, and use "-uw" to mount root read-write.
* Brooks pointed out a case where tmp needs to be run afterdougb2005-12-021-2/+1
| | | | mountcritremote, so force it the other way instead.
* Introduce startup scripts from the local_startup directories todougb2005-12-024-34/+83
| | | | | | | | | | | | | | | | the base rcorder. This is accomplished by running rcorder twice, first to get all the disks mounted (through mountcritremote), then again to include the local_startup directories. This dramatically changes the behavior of rc.d/localpkg, as all "local" scripts that have the new rc.d semantics are now run in the base rcorder, so only scripts that have not been converted yet will run in rc.d/localpkg. Make a similar change in rc.shutdown, and add some functions in rc.subr to support these changes. Bump __FreeBSD_version to reflect this change.
* Force this script to run before mountcritremote to avoiddougb2005-12-021-0/+1
| | | | | non-deterministic behavior when introducing local_startup scripts to rcorder.
* Add a -f configfile option to devd(8), based on a patch submitted byjkoshy2005-11-241-0/+1
| | | | | | Wojciech A. Koszek. Submitted by: Wojciech A. Koszek <dunstan@freebsd.czest.pl>
* Update the test for failed zone transfers to reflect BIND 9.3.1 semanticsdougb2005-11-221-10/+8
| | | | | | | | | | Simplify the shell scripting a bit, and remove a useless grep | sed The problem was pointed out by the PR, and I used part of the solution suggested there, but the semantics changed again for 9.2.x -> 9.3.x. PR: conf/74228 Submitted by: Jeremy Chadwick <freebsd@jdc.parodius.com>
* Remove not needed redirection of kldstat -q output to /dev/null.emax2005-11-222-2/+2
| | | | | Noticed by: pjd MFC after: 3 days
* Revise hcsecd(8) and sdpd(8) rc.d scripts one more timeemax2005-11-223-12/+28
| | | | | | | | | | - Use _prestart rc.d method to automatically kldload ng_btsocket(4) if needed; - Rename "sdpd_user" to "sdpd_username" and "sdpd_group" to "sdpd_groupname" to avoid collision with "magic" variables; Inspired by: yar MFC after: 3 days
* don't match packets other than IPv4 against divert rule.ume2005-11-181-1/+1
| | | | | | | | divert supports only IPv4. Reported by: SAITOU Toshihide <toshi__at__ruby.ocn.ne.jp> Discussed with: suz MFC after: 1 day
* Avoid invoking the current script again when we needyar2005-11-161-2/+3
| | | | | | | | | | | | | | to issue sub-commands, e.g., restart = stop + start. By calling run_rc_command instead, we provide rc.d scripts with full control over their configuration variables. For an example problem the former approach caused, see http://lists.freebsd.org/pipermail/freebsd-rc/2005-October/000311.html Reviewed by: freebsd-rc Tested by: Dirk Engling erdgeist <at> erdgeist.org MFC after: 2 weeks
* Diff reduction to RELENG_6.ru2005-11-161-4/+4
|
* Revise hcsecd(8) and sdpd(8) rc.d scripts.emax2005-11-152-6/+22
| | | | | | | | | | - Have both scripts automatically kldload ng_btsocket(4). I did not want to do it, but its easier for users and it seems other scripts do similar things; - Assign few variables after load_rc_config, so the /etc/rc.conf overrides actually work; MFC after: 1 week
* Add a new configuration variable, ipv4_addrs_<ifn>, which adds one orbrooks2005-11-143-2/+61
| | | | | | | | | | | more IPv4 address from a ranged list in CIRD notation: ipv4_addrs_ed0="192.168.0.1/24 192.168.1.1-5/28" In the process move alias processing into new ipv4_up/down functions to more toward a less IPv4 centric world. Submitted by: Philipp Wuensche <cryx dash freebsd at h3q dot com>
* Add section to start/stop Bluetooth USB devices (via ng_ubt(4))emax2005-11-121-0/+10
| | | | | | Submitted by: Panagiotis Astithas ( past at ebs dot gr ) Reviewed by: brooks, imp MFC after: 1 week
* Traditionally expand tabs here.ru2005-11-111-2/+2
|
* Add dev/speaker into include/ treedelphij2005-11-111-0/+2
|
* Start integrating Bluetooth into rc.d system.emax2005-11-106-5/+483
| | | | | | | | | | | | | | | | | | | | | | | | | Introduce /etc/rc.d/bluetooth script to start/stop Bluetooth devices. It will be called from devd(8) in response to device arrival/departure events. It is also possible to call it by hand to start/stop particular device without unplugging it. Introduce generic way to set configuration parameters for Bluetooth devices. By default /etc/rc.d/bluetooth script has hardwired defaults compatible with old rc.bluetooth from /usr/share/netgraph/bluetooth/examples. These can be overridden using /etc/defaults/bluetooth.device.conf file (system wide defaults). Finally, there could be another device specific override file located in /etc/bluetooth/$device.conf (where $device is ubt0, btccc0 etc.) The list of configuration parameters and their meaning described in the /etc/defaults/bluetooth.device.conf file. Even though Bluetooth device configuration files are not shell scripts, they must follow basic sh(1) syntax. The bluetooth.device.conf(5) and handbook update will follow shortly. Inspired by: Panagiotis Astithas ( past at ebs dot gr ) Reviewed by: brooks, yar MFC after: 1 week
* Backout r1.11...rse2005-11-101-1/+1
| | | | | | | | | | | | | | | | | | > > There is no need to explicitly add "status" to $extra_commands in > > the /etc/rc.d/pf script as it is implicitly added by /etc/rc.subr's > > run_rc_command() because of the existing $pf_program. > > > > Submitted by: Christoph Schug <chris@schug.net> ...because as yar@ points out: "[...] you were relying on evil side-effects of the variable being named *_program. hose side-effect have been eliminated since rc.subr rev. 1.42. [...] The point is that the default "status" method is for rc.d scripts that handle startup and shutdown of conventional daemons, and not for custom tasks like the pf case." The change is still valid in RELENG_6 (and still doesn't have to be backed out) as long as rc.subr:r1.42 is not MFC'ed to RELENG_6, too.
* Fix minor white space nit introduced in 1.102: use spaces, not tabs.rwatson2005-11-081-2/+2
|
* There is no need to explicitly add "status" to $extra_commands inrse2005-11-031-1/+1
| | | | | | | | the /etc/rc.d/pf script as it is implicitly added by /etc/rc.subr's run_rc_command() because of the existing $pf_program. Submitted by: Christoph Schug <chris@schug.net> MFC after: 1 week
* Add items to unmount to the front of the list so they are unmounted inbrooks2005-11-011-2/+2
| | | | reverse (thus allowing /conf to be unmounted).
* Switch from pax to tar for extracting cpio archives. pax requires abrooks2005-10-311-1/+1
| | | | | | | writable /tmp (or TMPDIR) and thus is unsuitable for this job. Tested by: Joerg Pulz <Joerg dot Pulz at frm2 dot tum dot de> PR: conf/88293
* The -x <format> option of pax is for creation of archives, notbrooks2005-10-311-1/+1
| | | | | | | | | | | extraction. This will allow cpio archive support to work, at least in situations where /tmp is writable. Because pax requires a writable /tmp it is unsuitable for this task, but replacing it will come in a later commit. Submitted by: Joerg Pulz <Joerg dot Pulz at frm2 dot tum dot de> PR: conf/88293
* Transforming "ppp-user" into just "ppp", step 5:yar2005-10-291-49/+0
| | | | Finally, delete the old, unfittingly named file "ppp-user".
* Transforming "ppp-user" into just "ppp", step 4:yar2005-10-291-1/+1
| | | | The legacy script "/etc/netstart" will start "ppp", not "ppp-user".
* Transforming "ppp-user" into just "ppp", step 3:yar2005-10-291-1/+1
| | | | Install "ppp" (just repocopied) instead of "ppp-user".
* Add some significant Ukrainian dates.ru2005-10-281-0/+2
| | | | | PR: 88076 Submitted by: Andriy Gapon
* Use ${name} in pathnames where appropriate.yar2005-10-285-7/+7
| | | | | The sendmail script already was on this way, but it didn't reach the end of it yet.
* Use:yar2005-10-282-2/+2
| | | | | | | | command="/path/to/${name}" since it's applicable here. It's the current style of rc.d. Pointed out by: pjd
* Transforming "ppp-user" into just "ppp", step 1:yar2005-10-285-5/+5
| | | | | | | | | | | The rcorder(8) condition PROVIDE'd by the script and REQUIRE'd by the others becomes "ppp". The ultimate goal of the transformation is to reduce confusion resulting from the fact that $name has been "ppp" already. Discussed with: pjd, -rc
* Override $command with $foo_program only if $commandyar2005-10-261-3/+1
| | | | | | | | | | has been set in the first place. This should reduce unwanted side-effects in rc.d scripts that don't mean to use $command and rc.subr(8) methods associated with it at all. Discussed with: brooks Reviewed by: -rc (silence)
* Document that `reload' is not provided by defaultyar2005-10-261-0/+2
| | | | yet it can be enabled when applicable.
* o Grammar.maxim2005-10-241-1/+1
| | | | | Submitted by: Ulrich Spoerlein MFC after: 1 week
* Don't be lazy, set the "command" variable even ifyar2005-10-235-0/+5
| | | | | | | | | | /etc/defaults/rc.conf will provide foo_program, too. By specifying "command" we explicitly say that we're going to rely on rc.subr(8) default methods, and rc.subr(8) will take advantage of this soon. The majority of our rc.d scripts already set "command" if appropriate, so fix just the non-compliant handful.
* wpa_supplicant(8) requires -D option for ndis(4) now.jkim2005-10-191-1/+10
|
* Allow the process name to be in square brackets ([]) in _find_processes().jhb2005-10-171-1/+1
| | | | | | PR: conf/82430 Submitted by: Pavel Volkov pol at iib dot ru MFC after: 1 week
* Remove redundant include.ru2005-10-141-1/+0
|
* First start rc.d/ipsec and then rc.d/mountcritremote, so we can mountpjd2005-10-122-2/+2
| | | | | | NFS file system over IPsec. Suggested by: Tomasz Pi³at <tomasz.pilat@axelspringer.pl>
* setkey(8) was repo-copied from usr.sbin/ to sbin/.pjd2005-10-121-1/+1
| | | | | | This will allow for NFS mount of /usr over IPsec. Discussed on: arch@
* Connect rc.d scripts for the hcsecd(8) and sdpd(8) daemons to the build.emax2005-10-121-1/+2
| | | | MFC after: 1 month
* Add rc.d scripts for the hcsecd(8) and sdpd(8) daemons. Put defaults intoemax2005-10-113-0/+53
| | | | | | | | | /etc/defaults/rc.conf. Both daemons can run even if no Bluetooth devices are attached to the system. Both daemons depend on Bluetooth socket layer and thus disabled by default. Bluetooth sockets layer must be either loaded as a module or compiled into kernel before the daemons can run. MFC after: 1 month
* stop RFC 4193 address on the outside interface.ume2005-10-051-0/+4
| | | | MFC after: 1 day
* Use more rc.subr bits to clean up pccard_ether and implement newbrooks2005-10-031-28/+42
| | | | | | | | features. Both the presence of a NOAUTO keyword and an interface being up can be ignored is the forcestart option is used. Additionally, a restart option has been added. Reviewed by: ume
* Add the lmcconfig tool for controlling the lmc driver. Add man pages andscottl2005-10-031-0/+2
| | | | | | glue. Submitted by: David Boggs
* Use available rc.subr features.yar2005-10-021-27/+16
| | | | | Reduce code duplication. Follow the current style of rc.d scripting.
* Record dependency on the newly introduced pfsync.yar2005-10-021-2/+2
| | | | | | | | | | | | | | Start before routing for better system protection. (pf used to start late during system boot, after many a network daemon have started already, which sucked from security POV.) Remark: For maximum security, pf should start before netif, but it would create a dependency loop because pfsync has to start after netif, yet before pf. Discussed with: mlaier on -pf MFC after: 5 days
* Add an rc.d script to start pfsync at the right moment of theyar2005-10-023-1/+57
| | | | | | | | | | | | | system boot, and hook it up in the system. The separate script is needed because in the presence of various interface lists in rc.conf ($network_interfaces, $cloned_interfaces, $sppp_interfaces, $gif_interfaces, more to come) it is hard to start them orderly, so that pfsync is brought up after its syncdev, which is required for the proper startup of pfsync. Discussed with: mlaier on -pf MFC after: 5 days
* Use rc.subr(8) appropriately:yar2005-10-021-44/+23
| | | | | | | | - utilize default methods instead of rolling local ones; - avoid to specify BEFORE conditions we don't really need (pflog will be REQUIRE'd by pf); - omit extra decoration from warning messages, warn() will decorate them sufficiently.
* o Remove unfinished code and make it possible to overridemaxim2005-10-021-14/+5
| | | | | | bsdextended_script from rc.conf(5): Not objected by: trhodes
OpenPOWER on IntegriCloud