summaryrefslogtreecommitdiffstats
path: root/etc
Commit message (Collapse)AuthorAgeFilesLines
* 1. Add missing semicolon between "warn" and "return" to make surerse2005-12-301-3/+3
| | | | | | | | | the line continuation backslash doesn't cause "warn" to print "return". 2. Group "warn" and "return" together as the "return 1" should be performed only if the "kldload nfsclient" also failed (and not already if the "vfs.nfs" sysctl(8) check failed). MFC after: 3 days
* Remove superfluous line continuation backslash.rse2005-12-301-1/+1
| | | | MFC after: 3 days
* Add a new extensible GSS-API layer which can support GSS-API plugins,dfr2005-12-296-0/+19
| | | | | | | | | similar the the Solaris implementation. Repackage the krb5 GSS mechanism as a plugin library for the new implementation. This also includes a comprehensive set of manpages for the GSS-API functions with text mostly taken from the RFC. Reviewed by: Love Hörnquist Åstrand <lha@it.su.se>, ru (build system), des (openssh parts)
* Fix another braino, don't remove the X related socket directoriesdougb2005-12-271-2/+5
| | | | | | right after creating them. Twiddle whitespace while I'm here.
* Make sure that the prestart routine is run with *start, instead ofdougb2005-12-271-1/+1
| | | | | | just 'start'. Reminded by: keramida
* syslogd should REQUIRE newsyslog, rather than newsyslog usingdougb2005-12-212-2/+1
| | | | | BEFORE: syslogd. This does not produce any change in the ordering at the moment, but is cleaner style for the long term.
* Several users have commented (via filing PRs) that having ntp* dependdougb2005-12-212-4/+1
| | | | | | | | | | on devfs is useful so that a hardware time device can start with its necessary device nodes already in place. While this ordering happens as a side effect currently in HEAD, and the PRs were generally fixed via upgrades, etc; it's better to make it explicit. While I'm here, ntpd should REQUIRE ntpdate, rather than ntpdate using BEFORE: ntpd.
* REQUIRE: syslogd and BEFORE: NETWORKING are now antithetical,dougb2005-12-211-1/+0
| | | | | | | | | | | and including both in this file had nasty side effects on the ordering of syslogd, as well as producing an error when running rcorder. Remove the more bogus of the two options, which restores proper ordering and removes the error. There is an open question as to whether scripts with the nostart KEYWORD should even have REQUIRE/BEFORE lines, and indeed, whether they should be in /etc/rc.d at all, but that's for another time.
* Include a somewhat hackish way to make sure that we *always* test thedougb2005-12-201-1/+6
| | | | new clear_tmp_X variable when start'ing.
* Brooks pointed out a potential problem with disabling the X cleaningdougb2005-12-202-10/+18
| | | | | | | | by default, so add a new knob that is on by default, and check that knob in start_precmd so that it can run even if cleaning /tmp is not enabled. This has the advantage of not violating POLA, while still allowing the user to disable this behavior if they wish (for example on a server that will never run X).
* Clear up problems with /etc/rc.d/{abi|cleanvar|cleartmp} broughtdougb2005-12-194-47/+71
| | | | | | | | | | | | | | | | | to light by the PR. Specifically, convert these three scripts into good rc.d citizens, making sure that their functionality is preserved, but the rc.d framework rules are not broken. Add support for cleanvar as a regular rc.d script in the default rc.conf, and document this in the man page. Add a descriptive comment to rc.conf that regarding the three emulation/compatibility services provided by abi so users will not be confused by these services not having their own startup scripts. PR: conf/84574 Submitted by: Alexander Botero-Lowry
* Remove usbd(8) and all references to it. It is no longer necessaryiedowse2005-12-156-33/+3
| | | | | | since devd(8) now provides the same functionality. Submitted by: Anish Mistry
* Add /boot/firmware as iwi(4) now reads its firmware there.delphij2005-12-111-0/+2
| | | | Reminded by: flz
* Move the remaining entries from usbd.conf to devd.conf. This nowiedowse2005-12-112-28/+29
| | | | | | | makes usbd redundant. PR: conf/73799 Submitted by: Anish Mistry
* Drop rcconf.sh now that it has been removeddougb2005-12-101-1/+1
|
* Remove rcconf.sh from /etc/rc.d, and instead load the configurationdougb2005-12-107-25/+17
| | | | | | | | | | | | | | | | as part of rc. Doing this, and the sourcing of rc.subr after we have determined if we are booting diskless (and correspondingly run rc.initdiskless if necessary) are safe, and actually allow fewer files to be needed on the diskless box. This also allows variables from the configuration to be available to rc itself, such as ... Add a variable to rc.conf, early_late_divider, which designates the script which separates the early and late stages of the boot process. Default this to mountcritlocal, and add text to etc/defaults/rc.conf, rc.conf(5) and diskless(8) which describes how and why one might want to change this. Reviewed by: brooks
* Silence a warning about empty directories in all the places it mightdougb2005-12-101-1/+1
| | | | | | occur. Reminded by: yar
* Use of REQUIRE is better than BEFORE for most scripts, and verydougb2005-12-101-1/+1
| | | | few scripts should have no REQUIRE at all.
* Files are installed with mode 444 by default.ru2005-12-091-1/+0
|
* Since rc.subr is a library of functions, it should not use exityar2005-12-061-6/+6
| | | | | | | | | | | | every now and then. It is up to the caller to choose a proper action upon an error condition. Therefore, use return, not exit, except for some special cases. Consistently return 1 to indicate an error. Submitted by: sem (initially) Reviewed by: freebsd-rc (silence) MFC after: 2 weeks
* Change how *.sh scripts are handled. If the script is in /etc/rc.d,dougb2005-12-051-2/+2
| | | | | | | | source it into the shell. If not, handle it in a subshell the same way that "real" rc.d-style scripts are handled. This will dramatically ease the "process local scripts in the base rcorder" transition. Add *.bak to the list of files in */rc.d that we ignore.
* 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.
OpenPOWER on IntegriCloud