summaryrefslogtreecommitdiffstats
path: root/etc/rc.d/bgfsck
Commit message (Collapse)AuthorAgeFilesLines
* - Add uid check.hrs2015-09-101-4/+11
| | | | | | - Report delay<0 as a warning. MFC after: 3 days
* s/-/_/ in name.hrs2014-10-121-1/+1
|
* Fix syntax errors (s/:=/:-/).dteske2012-07-191-1/+1
| | | | | | Reviewed by: emaste (mentor) Approved by: emaste (mentor) MFC after: 3 days
* Whitespace nitkevlo2012-07-131-1/+1
|
* Spelling fixes for etc/uqs2012-01-071-1/+1
|
* In regards to the "Starting foo:" type messages at boot time, create anddougb2009-10-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | employ a more generic solution, and use it in the individual rc.d scripts that also have an $rc_quiet test: 1. Add check_startmsgs() to rc.subr. 2. In the rc.d scripts that use rc_quiet (and rc.subr) substitute variations of [ -z "$rc_quiet" ] with check_startmsgs 3. In savecore add a trailing '.' to the end of the message to make it more consistent with other scripts. 4. In newsyslog remove a : before the terminal '.' since we do not expect there to be anything printed out in between to make it more consistent. 5. In the following scripts change "quotes" to 'quotes' where no variables exist in the message: savecore pf newsyslog 6. In the following scripts substitute if/then/fi for the simpler (and more consistent) check_startmsgs &&: faith stf 7. In the following scripts separate the "Starting foo:" from the terminal '.' to make them more consistent: moused hostname pf 8. In nfsclient move the message to its own line to avoid a style bug 9. In pf rc_quiet does not apply to the _stop method, so remove the test there. 10. In motd add 'quotes' around the terminal '.' for consistency
* As previously discussed, add the svn:executable property to all scriptsdougb2008-07-161-0/+0
|
* Move a lot of diagnostic output behind $rc_quiet in scripts thatmtm2008-06-231-1/+1
| | | | implement their own start command.
* Allow background_fsck_delay to be set to a negative value which delaysbrooks2007-03-111-2/+14
| | | | | | | the background fsck indefinitely. This allows the administrator to run it at a convenient time. To support running it from cron, the forcestart argument now causes the fsck to start with no delay and all output to be suppressed.
* This depends on syslogd due to logger(1).obrien2005-07-221-1/+1
|
* Remove the requirement for the FreeBSD keyword as it no longermtm2004-10-071-1/+1
| | | | | | | makes any sense. Discussed with: dougb, brooks MFC after: 3 days
* Mark scripts as not usable inside a jail by adding keyword 'nojail'.pjd2004-03-081-1/+1
| | | | Some suggestions from: rwatson, Ruben de Groot <mail25@bzerk.org>
* Set appropriate tag "fsck" to logger(1) for background fsck messages.matusita2003-04-231-1/+1
| | | | | PR: 51174 Submitted by: Alex Popa <razor@ldc.ro>
* Delay an optional amount of time after booting before starting amckusick2002-12-181-2/+13
| | | | | | | | | background fsck. The delay defaults to sixty seconds to allow large applications such as the X server to start before disk I/O bandwidth is monopolized by fsck. Submitted by: Brooks Davis <brooks@one-eyed-alien.net> Sponsored by: DARPA & NAI Labs.
* Add a period to the end of the "starting" message to be consistentdd2002-07-281-1/+1
| | | | with the rest of the output during a boot.
* Merge in all the changes that Mike Makonnen has been maintaining for agordon2002-06-131-0/+19
while. This is only the script pieces, the glue for the build comes next. Submitted by: Mike Makonnen <makonnen@pacbell.net> Reviewed by: silence on -current and -hackers Prodded by: rwatson
OpenPOWER on IntegriCloud