| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
PR: 179828
|
|
|
|
|
|
|
| |
Sorry, that would break users running head and BIND from ports, since
ports rely on these scripts. The ports will be fixed soon.
Reviewed by: erwin
|
|
|
|
|
|
|
|
|
|
| |
Add netif as a requirement of syslogd to get lo0 up. Currently, this
doesn't affect the rc order, because mountcritremote already depends on
netif.
Reviewed by: eadler
Approved by: kenm (mentor)
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
| |
systems are fully "ready to go".
'FILESYSTEMS' states: "This is a dummy dependency, for services which
require file systems to be mounted before starting." However, we have
'var' which is was run after 'FILESYSTEMS' and can mount /var if it
already isn't mounted. Furthermore, several scripts cannot use /var
until 'cleanvar' has done its thing. Thus "FILESYSTEMS" hasn't really
meant all critical file systems are fully usable.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
with theirs, so this information doesn't need to be in the live file.
Having it in our CVS history is enough.
|
|
|
|
|
|
|
|
|
| |
scripts, except for mdconfig* and jail. Such symbols are reserved
for the rc.subr internals. Most scripts can be fixed by just
declaring _foo symbols as local: few scripts actually need them to
be global.
Discussed with: dougb in freebsd-rc
|
|
|
|
|
| |
BEFORE: syslogd. This does not produce any change in the
ordering at the moment, but is cleaner style for the long term.
|
|
|
|
|
|
|
| |
makes any sense.
Discussed with: dougb, brooks
MFC after: 3 days
|
|
|
|
|
|
|
| |
Otherwise it could be in the situation where its log socket is removed
after it has started.
Noticed by: jhay
|
|
|
|
| |
hold-overs from the initial NetBSD import.
|
| |
|
|
|
|
|
|
|
|
|
| |
in keeping the scripts under rc.d in sync with us. So, remove
NetBSD specific stuff (which made our scripts more complicated
than necessary).
The NetBSD ident string will be left intact, both for history and
also incase we wish to pull in future versions.
|
|
|
|
|
|
| |
in keeping the scripts under rc.d in sync with us. So, begin removal
of NetBSD specific stuff (which made our scripts more complicated
than necessary), starting with the NetBSD KEYWORD.
|
|
|
|
| |
PR: bin/40846
|
|
|
|
| |
OS-dependent case switches.
|
|
|
|
|
|
|
|
| |
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
|
|
Note that `rc' and `rc.shutdown' could not be imported because we already
have files with those names.
|