summaryrefslogtreecommitdiffstats
path: root/etc/rc.d
Commit message (Collapse)AuthorAgeFilesLines
* Correct style.obrien2012-08-221-1/+1
|
* * Reinstate r128059's consumption of our best entropy first.obrien2012-08-221-8/+13
| | | | | | | | | r128060 for "hardware-supplied entropy" reversed this without reason, seems a typo. * Isolate "better than nothing" implementation to a function. Submitted by: obrien & Arthur Mesh <arthurmesh@gmail.com> Sponsored by: Juniper Networks
* The entire comment block is now spell checked this time -- I promise.obrien2012-08-221-2/+2
|
* Allow - be used in the name of a provider. Without this change it's notdelphij2012-08-222-2/+2
| | | | possible to specify a gptid in geli_devices.
* Fix comment misspelling.obrien2012-08-221-1/+1
| | | | Submitted by: kargl
* Depend on the new 'postrandom' instead of random.obrien2012-08-221-1/+1
| | | | | We need to limit the amount of time between consuming the entropy seeds and removing it in case of a kernel panic.
* Remove old entropy seeding after consumption initializing /dev/random PRNG.obrien2012-08-222-1/+45
| | | | | | | Not doing so opens us up to replay attacks. Submitted by: Arthur Mesh <arthurmesh@gmail.com> Sponsored by: Juniper Networks
* Add dependencies based on security(7).obrien2012-08-221-0/+1
|
* - Allow to pass extra parameters for each jails.kuriyama2012-08-191-5/+19
| | | | | | | - To achieve above, convert jail(8) invocation to use new style command line "-c" flag. Reviewed at: freebsd-jail@
* Revert SVN r238628 (mistake).dteske2012-07-191-1/+1
|
* Fix syntax errors (s/:=/:-/).dteske2012-07-192-2/+2
| | | | | | Reviewed by: emaste (mentor) Approved by: emaste (mentor) MFC after: 3 days
* Allow to specify no source-address-selection policyemax2012-07-191-0/+3
| | | | MFC after: 1 week
* Move -n ${_jail} before ${_flags} so that any -n options in ${_flags}des2012-07-181-1/+1
| | | | will override ours instead of the other way around.
* MFP4 214344:brooks2012-07-131-1/+1
| | | | | | | Tighten the regular expression that checks for an md /tmp such that no /tmp mount and an md / isn't improperly matched. Sponsored by: DARPA/AFRL
* Whitespace nitkevlo2012-07-138-10/+10
|
* - Add IFT_L2VLAN (vlan(4)) support.hrs2012-07-091-1/+2
| | | | | | - Add -P option to support PID file. When -a is specified /var/run/rarpd.pid is used, and when an interface is specified /var/run/rarpd.<ifname>.pid is used by default.
* Make ipfw0 logging pseudo-interface clonable. It can be created automaticallyhrs2012-07-091-0/+4
| | | | | | | by $firewall_logif rc.conf(5) variable at boot time or manually by ifconfig(8) after a boot. Discussed on: freebsd-ipfw@
* Name jails automatically.des2012-07-041-1/+1
| | | | MFC after: 1 week
* Revert r238004 as more review has come in and there is now a discussionsbruno2012-07-021-1/+1
| | | | on how to best proceed.
* Cosmetic display change of Cx states via cx_supported sysctl entries.sbruno2012-07-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Adjust power_profile script to handle the new world order as well. Some vendors are opting out of a C2 state and only defining C1 & C3. This leads the acpi_cpu display to indicate that the machine supports C1 & C2 which is caused by the (mis)use of the index of the cx_state array as the ACPI_STATE_CX value. e.g. the code was pretending that cx_state[i] would always convert to i by subtracting 1. cx_state[2] == ACPI_STATE_C3 cx_state[1] == ACPI_STATE_C2 cx_state[0] == ACPI_STATE_C1 however, on certain machines this would lead to cx_state[1] == ACPI_STATE_C3 cx_state[0] == ACPI_STATE_C1 This didn't break anything but led to a display of: * dev.cpu.0.cx_supported: C1/1 C2/96 Instead of * dev.cpu.0.cx_supported: C1/1 C3/96 MFC after: 2 weeks
* - Change kfd rc script to be more conformant with rcNG conventions:stas2012-05-061-7/+5
| | | | | | | | | | o change rcname to kfd; o move mandatory options to command_args; o add missing "shutdown" keyword; o fix require line. Kfd doesn't really need to be started before daemons. Suggested by: dougb
* - Don't log messages saying that accounting is being disabled and enabledjhb2012-05-021-3/+1
| | | | | | | | | | if the accounting log file is atomically replaced with a new file (such as during log rotation). - Simplify accounting log rotation a bit. There is no need to re-run accton(8) after renaming the new log file to it's real name. PR: kern/167321 Tested by: Jeremy Chadwick
* - Add rc.d script for kfd, kerberos forwarded tickets daemon.stas2012-04-102-0/+20
|
* Rather than printing the output from route add for all FIBs just print thembz2012-03-041-16/+30
| | | | | | | | | for the default FIB followed by a statement with a list of FIB numbers for all the other FIBs we install the routes for. Request by: kib (to make it less noisy) Tested by: kib MFC after: 3 days
* Merge multi-FIB IPv6 support from projects/multi-fibv6/head/:bz2012-02-171-5/+21
| | | | | | | | | | | | Extend the so far IPv4-only support for multiple routing tables (FIBs) introduced in r178888 to IPv6 providing feature parity. This includes an extended rtalloc(9) KPI for IPv6, the necessary adjustments to the network stack, and user land support as in netstat. Sponsored by: Cisco Systems, Inc. Reviewed by: melifaro (basically) MFC after: 10 days
* Fix various issues with the NFS and RPC related scripts:dougb2012-02-1413-144/+55
| | | | | | | | | | | | | | | | | | | 1. Add new functionality to the force_depend method to incorporate the tests for whether the service is enabled and/or already running. 2. Add a new option to bypass checking only that the service is enabled at boot time, and always check if it is running. 3. Use this new functionality to greatly simplify the rc.d scripts that use force_depend. 4. Add a force_depend for statd in lockd 5. Remove the check that either nfs_server or nfs_client is _enable'd from statd and lockd. This was always overkill, and prevented using the {one|force}start options, as well as stop'ing on the command line. 6. The yp* scripts had some of their arguments in various weird orders. Bring them into line with the model. 7. If mountd fails to create /var/db/mountdtab, err out. Ideas, suggestions, and/or review from delphij and jilles. Pointy hats are completely my responsibility however.
* start watchdogd before most of other daemons/serversavg2012-02-122-2/+2
| | | | | | | | | The main benefit is that watchdogd would shutdown after most of other daemons/servers and thus, for example, would remedy a system hang caused by unlucky X server shutdown. Reviewed by: dougb (earlier version) MFC after: 2 weeks
* Avoid using BEFORE in the utx rc script.ed2012-02-122-2/+1
| | | | Requested by: dougb
* Move utmpx handling out of init(8).ed2012-02-113-2/+23
| | | | | | | | | | | | | | | | | This has the following advantages: - During boot, the BOOT_TIME record is now written right after the file systems become writable, but before users are allowed to log in. This means that they can't cause `hidden logins' by logging in right before init(8) kicks in. - The pututxline(3) function may potentially block on file locking, though this is very rare to occur. By placing it in an rc script, the user can still kill it with ^C if needed. - Most importantly: jails don't use init(8). This means that a force reboot of a system running jails will leave stale entries in the accounting database of the jails individually.
* In the days before r208307 addswap was running early in the second stagedougb2012-02-112-2/+2
| | | | | | | | of rcorder. Somehow in the intervening period addswap got moved to the very end, which is almost certainly not what we want. This change moves it to right after kld so that for users who need it, they'll get it ASAP.
* As it stands right now, the default devfs rulesets are only loaded as adougb2012-02-081-1/+2
| | | | | | | | | side effect of something else using them. If they haven't been loaded already but you want to use them, say for configuring a jail, you're out of luck. So add a knob to always load the default rulesets. While I'm here document the other devfs_ knobs in rc.conf.5.
* Fix $ipv6_network_interfaces handling in rc.d/routing. It could fail whenhrs2012-02-041-2/+4
| | | | | | it was set to "auto", for example. MFC after: 3 days
* Perform IPv6 DAD only in ifn_start.hrs2012-01-291-2/+4
|
* Fix several glitches in IPv6-related knobs:hrs2012-01-221-0/+10
| | | | | | | | | | | | | | - ipv6_enable + ipv6_gateway_enable should unset ACCEPT_RTADV by default for backward compatibility. - Configurations in ipv6_prefix_IF should be recognized even if there is no ifconfig_IF_ipv6. - DAD wait should be performed at once, not on a per-interface basis, if possible. This fixes an issue that a system with a lot of IPv6-capable interfaces takes too long for booting. MFC after: 1 week
* When creating the jails /dev/log symlink, do it by full path to avoidbrooks2012-01-201-4/+1
| | | | | | | | | | creating stray "log" symlinks if the mount fails. That apparently happens in some ezjail configs. PR: conf/143084 Submitted by: Dirk Engling <erdgeist at erdgeist.org> Reviewed by: simon MFC after: 2 weeks
* dhclient: don't use syslog for logging non-DHCP interface errorsrea2012-01-201-2/+2
| | | | | | We should show the error to user, but it doesn't deserve syslog. Approved by: jhb
* Prepare for the removal of set_rcvar() by changing the rcvar=dougb2012-01-1466-70/+70
| | | | | | | | | | | | | | | 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.
* rc.d: document 'quiet' prefix and fix dhclient/devd interactionrea2012-01-121-1/+8
| | | | | | | | | | | | | | | | | | | | | Document the current semantics of the 'quiet' command prefix in the rc.subr(8). Fix dhclient rc.d script: it should not call err() for non-DHCP-enabled interface when it is called from devd, because the latter just blindly calls 'service dhclient quietstart' on each "link up" event. Since the 'quietstart' will silence the message "Cannot 'start' <foo>. Set <foo>_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'." and running dhclient on the non-DHCP-enabled interface is the same thing as running the service <foo> without <foo>_enable set, such modification is in sync with the current semantics of the 'quiet' prefix. Approved by: glebius Reviewed by: freebsd-rc list MFC after: 2 weeks
* Bunch of fixes to pfsync(4) module load/unload:glebius2012-01-091-7/+0
| | | | | | | | | | | | | | | | | | | | | o Make the pfsync.ko actually usable. Before this change loading it didn't register protosw, so was a nop. However, a module /boot/kernel did confused users. o Rewrite the way we are joining multicast group: - Move multicast initialization/destruction to separate functions. - Don't allocate memory if we aren't going to join a multicast group. - Use modern API for joining/leaving multicast group. - Now the utterly wrong pfsync_ifdetach() isn't needed. o Move module initialization from SYSINIT(9) to moduledata_t method. o Refuse to unload module, unless asked forcibly. o Improve a bit some FreeBSD porting code: - Use separate malloc type. - Simplify swi sheduling. This change is probably wrong from VIMAGE viewpoint, however pfsync wasn't VIMAGE-correct before this change, too. Glanced at by: bz
* There is no longer a need to abstract ${rcvar_manpage} as we are notdougb2012-01-081-1/+1
| | | | attempting to maintain compatibility with NetBSD for some years now.
* Spelling fixes for etc/uqs2012-01-071-1/+1
|
* Add 'nojail' keyword as auditd(8) can't really do anything useful whenpjd2012-01-061-1/+1
| | | | | | | inside a jail. Discussed with: rwatson MFC after: 1 week
* - Put one file into one line. This makes keeping local changes and mergingpjd2011-12-151-39/+154
| | | | | | | | | with FreeBSD easier for vendors. - For optional files use variables starting with underscore. Both changes make rc.d/Makefile look similar to sys/modules/Makefile. Reviewed by: dim
* Ensure kldxref is run first. Currently both 'kldxref' and 'kld' dependobrien2011-12-011-1/+1
| | | | | | on "FILESYSTEMS" and 'kld' is being run 8 scripts ahead of 'kldxref'. Reported by: dhw
* rc.d: Eliminate some unnecessary non-POSIX constructs:jilles2011-11-082-1/+2
| | | | | | * set - ... * empty braces * ^ in character class
* Whenever you boot with nfsv4_server_enable=NO (the default) in rc.conf,dim2011-11-051-0/+5
| | | | | | | | | | | | | | | | | | | the /etc/rc.d/nfsd script sets vfs.nfsd.server_max_nfsvers to 3. Then, when you set nfsv4_server_enable=YES in rc.conf, and restart nfsd via the rc.d script, without rebooting, the sysctl does *not* get reset to max version 4, so NFSv4 still doesn't work. Fix this by explicitly setting vfs.nfsd.server_max_nfsvers to 4 when NFSv4 is requested. I also added resetting of the nfs_privport sysctls, since this has the same issue: nfs_reserved_port_only=YES in rc.conf sets the nfs_privport sysctl to 1, but in the other case, the sysctl doesn't get reset to 0. Reviewed by: rmacklem Silence from: rc@ MFC after: 3 days
* Fix handling of rc_force in /etc/rc.d/dhclientrea2011-10-281-4/+13
| | | | | | | | | | Variable 'rc_force' is accessible only at the time of rc_run_command, so it can't be examined from the script's main code. Spotted by: hrs Reviewed by: hrs, des Approved by: des MFC after: 2 weeks
* Correctly reassign copyright of etc/rc.d/static_ndp back to delphij@mm2011-10-231-1/+1
| | | | | | | as the project itself is no legal entity Reported by: Joe Dahl <joel@vnode.se> MFC after: 3 days
* Add etc/rc.d/static_ndp, analogous to etc/rc.d/static_arp.mm2011-10-233-1/+76
| | | | | | | | | | Make sure that static ARP and NDP bindings are set before NETWORKING. As static_ndp is based on static_arp, pass copyright to the project with permission of the original author (delphij@). Reviewed by: delphij@FreeBSD.org MFC after: 3 days
* The rc_force test was inverted in the previous commit, so that dhclient randes2011-10-171-1/+1
| | | | | | | | | | | for interfaces which were not configured for DHCP *unless* rc_force was set; the correct logic is to run dhclient for those interfaces *only if* rc_force is set. Broken by: des@ Noticed by: everybody and his dog Submitted by: rea@ PR: bin/161733
OpenPOWER on IntegriCloud