summaryrefslogtreecommitdiffstats
path: root/etc/rc
Commit message (Collapse)AuthorAgeFilesLines
...
* Don't protect savecore(8) from being run with a bad dumpdircjc2002-03-111-3/+8
| | | | | | | | | | argument. Don't fail silently, but let savecore(8) make noise. It won't behave badly, it doesn't need protection. At the same time, allow the administrator to have dumpdev enabled while dumpdir (savecore(8)) is disabled and document how to do it. PR: conf/35725
* Add infrastructure for sendmail 8.12. If users are not starting a daemongshapiro2002-02-171-1/+16
| | | | | | | | | | | | | at boot (sendmail_enable=NO), a localhost-only daemon may started (sendmail_submit_enable) as it is needed to accept mail from command line submissions. If this isn't desired, see etc/mail/README for more hints. Optionally (sendmail_msp_queue_enable) start a queue runner for the submission queue in case a daemon isn't available to accept command line submitted mail at submission time. Note that the syslog labels for all of these sendmail processes have been uniquified for easier log parsing.
* Remove check for sendmail.conf before even trying to start sendmail.cjc2002-02-171-12/+10
| | | | | | | | | | | | Checking for the existence of sendmail.cf is rather silly when someone is using the mailwrapper(8) to run a mail daemon that is not actually sendmail(8). It is also probably better to let sendmail(8) actually try to start and error out if the administrator has 'sendmail_enable="YES"' but no sendmail.conf. At present, it would fail silently. Reviewed by: gshapiro MFC after: 2 days
* Use MACHINE_ARCH instead of MACHINE to check i386 arch.nyan2002-02-041-2/+2
| | | | MFC after: 3 days
* Register amd's dependency on NFS.sheldonh2002-01-281-0/+1
| | | | | | | | This change was submitted to the freebsd-audit mailing list for review but received no feedback. Hindsight-enabled reviews are welcome. PR: conf/31358 Submitted: Thomas Quinot <thomas@cuivre.fr.eu.org>
* Don't require operators to override the list of network filesystemsheldonh2001-12-291-3/+11
| | | | | | | | | | | | | | | | types (networkfs_types) with a version that includes the original list. This increases the scope for user error and also means that systems with networkfs_types set in /etc/rc.conf will not benefit from changes to the list in /etc/defaults/rc.conf on upgrade. Instead, store the default list in /etc/rc itself and allow the operator to append to that list by specifying her own list in networkfs_types. Rename networkfs_types to extra_netfs_types accordingly, as the new name better describes the purpose of the variable. Default the value to 'NO'.
* Re-introduce the fix that delays mounting of network filesystems untilsheldonh2001-12-271-1/+32
| | | | | | | | | | | | | | | | | | the network is initialized. This was first implemented in rev 1.268 of src/etc/rc, but was backed out at wollman's request. The objection was that the right place for the fix is in mount(8). Having looked at that problem, I find it hard to believe that the hoops one would have to jump through can be justified by the desire for purity alone. Note that there are reported issues surrounding nfsclient kernel support and mount_nfs(8), which currently make NFS an ugly exception to the general case. With this change, systems with non-NFS network filesystems configured for mounting on startup in /etc/fstab are no longer guaranteed to fail on startup.
* Don't assume that /var/run and /var/spool/lock are on the samebrian2001-12-191-10/+13
| | | | | | partition. Submitted by: ru
* Set the script_name_sep variable to a safe value if it is notroam2001-12-121-0/+3
| | | | | | | | | | | | already set (e.g. a failed/skipped mergemaster run during an upgrade). Without this, if script_name_sep was not set in the rc.conf files, local scripts will not be executed on startup or shutdown. PR: misc/32687 Submitted by: Nicholas Paufler <echofox@discordia.ca> (the problem) Sheldon Hearn (the idea behind the fix) Reviewed by: sheldonh MFC after: 1 week
* s/sysctl -w/sysctl/ru2001-12-111-4/+4
|
* Handle the lack of nfs server or client support in the kernel bydougb2001-10-191-3/+18
| | | | kldload'ing the appropriate modules before enabling the service.
* Follow existing style a little betterdougb2001-10-101-3/+6
|
* Add a dumpdir variable that determines where savecore stores crash dumps.des2001-10-091-2/+5
| | | | I've had this on my development box for ages...
* Sigh, fix the unfixed typo: s/-l/-L/.ru2001-10-021-1/+1
|
* Fix a typo: s/-or/-o/.knu2001-10-021-1/+1
|
* Add ()'s around the warning message when skipping a startup script.obrien2001-10-011-1/+1
| | | | | | | Also don't give the whole path, just the script name. Submitted by: des Requested by: jhb
* Tweak the Skipping ${script} logic to also handle symlinks.obrien2001-10-011-2/+2
| | | | Also echo with "-n".
* Fix the problem that the startup directory is printed out if itobrien2001-09-301-1/+1
| | | | | | is empty. Submitted by: Udo Schweigert <udo.schweigert@siemens.com>
* Give people a chance to do things before fsck is run.phk2001-09-261-0/+6
| | | | MFC after: 2 weeks
* Run rc.devfs a little bit earlier.obrien2001-09-261-6/+6
| | | | | | | Many people like to use generic devices in rc.syscons, etc.. So rc.devfs needs to run before those rc files. Requested by: Jos Backus <josb@cncdsl.com>
* Let people know when a startup script is skipped because it is notobrien2001-09-251-0/+2
| | | | | | executable. Suggested by: gad
* Back out rev 1.274. The previous behavior was documented in rc.8 andobrien2001-09-241-1/+1
| | | | | | | the original commit of local_startup depended on the scripts being executable; so there is too much precedence to change it now. About all anyone could agree on is that rev 1.274 broke POLA and before rev 1.274 also broke POLA.
* + explicitly use the shell to run ${local_startup} so one does not have toobrien2001-09-241-2/+2
| | | | | ensure the executable bit is set on the scripts. + Fix VCS ID's
* Remove more vestages of diskcheckd, which is now in ports/sysutils.obrien2001-08-291-8/+0
|
* Add a script_name_sep rc.conf knob to specify the IFS characterroam2001-07-171-5/+12
| | | | | | | | | | for separating the startup scripts' list into individual filenames. Run the shutdown scripts in reverse alphabetical order, so dependent services are stopped before the services they depend upon. Reviewed by: -arch, -audit MFC after: 3 weeks
* Reduce chattiness of entropy file mechanism with extreme prejudice.rwatson2001-06-281-1/+1
| | | | Reviewed by: USENIX Cabal (peter, jhb, wpaul, et al)
* Introduce syslogd_program and inetd_program variables in case somebodydd2001-06-281-2/+3
| | | | | | | wants to replace one of those programs. PR: 13609 Submitted by: Goran Lowkrantz <goran.lowkrantz@infologigruppen.se>
* Back out rev 1.268.sheldonh2001-06-101-21/+10
| | | | Requested by: wollman, rwatson
* Fix /etc/rc so that all remote filesystems, not just NFS, are mountedsheldonh2001-06-091-10/+21
| | | | | | | | | | after the network is configured. Future remote filesystem types should be added to remote_fstypes, which is a whitespace-delimited list of type:description pairs. The specific problem this fixes right now is that smbfs mounts described in /etc/ftsab were failing.
* Add diskcheckd to /etc/rc with a knob in rc.conf.phk2001-06-031-0/+8
| | | | | | | Make the default setting YES for now to get some experience with it. Note: If people starts seeing disk errors because of this then it should not be backed.
* Don't confuse the admin with spurious error messagesyar2001-05-271-1/+1
| | | | | | | | | | about non-existent mount directories (which would come into existence after the real mount has occured) when just testing for if there are any NFS filesystems in /etc/fstab. PR: bin/26597 Submitted by: Dmitry Morozovsky <marck@rinet.ru> MFC after: 3 days
* Introduce a background_fsck rc.conf option which allows the user todd2001-05-221-6/+15
| | | | | | | enable or disable background fsck'ing all in one shot. Default is currently 'YES'. Reviewed by: jkh
* Back out rev 1.260. The 'streams' module is a registered dependency ofpeter2001-05-131-3/+1
| | | | | the 'svr4' module already. This was a 4.x-only problem and should not have been MFS'ed.
* Update the fsck command in /etc/rc to use the new backgroundmckusick2001-05-111-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fsck checking. Applying these changes (typically via mergemaster) will cause your system to start running background checks on all your soft update enabled filesystems (provided that you have a kernel with the required functionality, e.g., one built since the end of April). Please report any and all problems to mckusick@mckusick.com (not mckusick@freebsd.org which I read infrequently). See the comment above the fsck command in /etc/rc for instructions on how to disable background checking should it cause you too much trouble. Several FAQs: 1) Can I reboot before the background checks are done? Ans) Yes, when the system restarts the checks will pick up where they left off. 2) Can a crash during checking corrupt my filesystem? Ans) No, recovered resources are returned to the system using soft updates which ensure that the freeing is done in a safe order. 3) How will I know if any background checks are being done? Ans) Filesystems that are to be checked in background will be listed as `DEFER FOR BACKGROUND CHECKING' at the usual fsck check time during system startup. 4) What happens to the output of the background checks? Ans) It is sent to syslog `daemon' facility log level `notice'. 5) When will this feature be available in the 4.X kernel? Ans) Never. It is much too radical and extensive a change to be MFC'ed. Besides, it needs many months of experience and tuning before it is ready for widespread use. 6) What happens if a background fsck fails (i.e., fsck finds errors that would normally require a manual fsck)? Ans) The filesystem will be marked as needing a manual fsck. At the next system reboot, the check will be done in foreground and the usual actions taken (usually a failure to go multi-user until fsck has been run by hand on the affected filesystem).
* Delete everything that's not a directory in /var/run and /var/spool/lockbrian2001-05-101-2/+5
| | | | | | at boot time. MFC after: 3 weeks
* In the /etc/rc startup script a soft link is created from /var/run/log tophk2001-04-151-1/+1
| | | | | | | | | | /dev/log like this: if [ ! -h /dev/log ]; The man page for test(1) says that the -h switch is depracated and that users should NOT rely on it being available. It suggest the -L switch instead. They both do the same thing: check for the existence of the symbolic link. PR: 26596 Submitted by: mikem <mike_makonnen@yahoo.com>
* MFS: deal with svr4 module's dependency on streams modulejkh2001-04-141-1/+3
|
* vnconfig(8) -> mdconfig(8).ru2001-04-101-2/+2
| | | | Reviewed by: phk
* Remove sockets found in /var/run or /var/spool/lock at boot timebrian2001-03-281-1/+1
| | | | (as well as files).
* At great personal risk, touch the sendmail startup again. This adds easypeter2001-03-131-8/+17
| | | | | seperate knobs for inbound (accepting SMTP connections) and outbound (just occasionally dequeueing) sendmail daemon startup.
* Add flags option for savecore.dougb2001-03-121-2/+2
| | | | Submitted by: David A. Panariti <davep@who.net>
* The /dev/random harvesting sysctls have had a name change.markm2001-03-101-3/+3
| | | | Reflect this.
* Avoid complicated tests of whether devices are present or not, anddougb2001-03-101-48/+10
| | | | | | | | | | enable all harvesting options by default since having them on for devices not present doesn't hurt anything. Leave them on by default since for the most part they are not producing noticable slowdown, and are about to get a lot more efficient. Re-order part of the cheesy entropy process in preparation for its complete removal.
* Add code to turn on the entropy harvesting sysctl's as early as possibledougb2001-03-011-0/+78
| | | | | | during the boot process. We're turning it on by default, based on the actual presence of a configured ethernet card, and/or ppp/tun devices. Of course, it's easy to disable in rc.conf.
* Introduce the option of running fsck -y if the initial preen fails.dougb2001-02-051-2/+18
| | | | | | Defaults to off. Obtained from: Yahoo!
* Run purgedir (a local function) on /var/run instead of rm /var/run/*brian2001-01-301-2/+1
| | | | | PR: 24612 Submitted by: David Drum <david@mu.org>
* Add the options of which cron program to run, and specifying flagsdougb2001-01-211-1/+1
| | | | | | | to it. PR: conf/24358 Submitted by: Gerhard Sittig <Gerhard.Sittig@gmx.net>
* Add a sysvipc_enable variable that causes the SysV IPC modules to be loaded.des2001-01-161-0/+10
| | | | Reviewed by: dougb
* Move the process of storing entropy from /dev/random and reseeding withdougb2001-01-141-54/+33
| | | | | | | | | | | | | | | | it at boot time closer to the way we want it to be in the final version. * Move the default directory to /var/db/entropy * Run the entropy saving cron job every 11 minutes. This seems to be a better default, although still bikeshed material. * Feed /dev/random some cheesy "entropy" from various commands and files before the disks are mounted. This gives /dev/random a better chance of running without blocking early. * Move the reseeding with previously stored entropy to the point immediately after the disks are mounted. * Make the harvesting script a little safer in regards to the possibility of accidentally overwriting something other than a regular file.
* Add a system to save entropy from /dev/random periodically so thatdougb2001-01-111-10/+26
| | | | | | | | | | | | | | | | | | it can be used to reseed at boot time. This will greatly increase the chances that there will be sufficient entropy available at boot time to prevent long delays. For /etc/rc, remove the vmstat and iostat runs from the attempt to provide some cheesy randomness if the files fail, since those programs are dynamically linked, and ldd seems to want some randomness to do its magic. Guidance and parameters for this project were provided by Mark Murray, based on the requirements of the Yarrow algorithm. Some helpful suggestions for implementation (including the tip about iostat and vmstat) were provided by Sheldon Hearn. All blame for problems or mistakes is mine of course.
OpenPOWER on IntegriCloud