| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
rc.d/routing and in to rc.d/netoptions. Also instead of saying
"TCP options" say "IP options".
|
|
|
|
|
|
|
|
| |
dependency was introduced because this script had rc.d/localpkg (which is
*after* rc.d/NETWORKING) in its REQUIRE line.
From an examination of its contents it seems that only the availability of
a local filesystem is necessary for this script to function properly.
|
|
|
|
|
|
|
| |
'zfs mount -a' from the main system - this is by design, as mountpoint
may be set to dangerous value. This all means, that such file system
has to be mounted from within a jail. To make it easier, reorganize
rc.d/zfs script so it can be used from within a jail.
|
|
|
|
| |
Submitted by: rodrigc (BSD.include.dist).
|
|
|
|
|
|
| |
device.
Discussed with: des
|
| |
|
|
|
|
|
|
|
|
|
|
| |
NFS-share anything. This way we can safely start mountd with
/etc/zfs/exports and mountd won't complain.
Pointed out by: ceri
- Move 'zfs volinit' before 'zfs mount -a' and 'zfs volfini' after
'zfs unmount -a'.
|
|
|
|
| |
open, so we not longer has to check if /etc/zfs/exports exists.
|
|
|
|
|
| |
we don't do this and the file doesn't exist mountd(8) will abort.
o The mountd(8) daemon creates a pidfile, so use it.
|
|
|
|
|
|
|
|
|
| |
daemon. The FreeBSD port print/hplip currently provides these services.
PR: conf/99593
Submitted by: Anish Mistry <amistry@am-productions.biz>
Approved by: maxim
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
current misc/amanda-server code uses it.
PR: conf/111050
Submitted by: Charles Sprickman<spork@bway.net>
Approved by: maxim
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The registration names for 5222(tcp,udp) and 5269(tcp,udp) was changed to
xmpp-client and xmpp-server correspondingly.
This inconsistency causes problems to applications developed on other
systems, as they tries to use port numbers from /etc/services as fallback.
PR: conf/100606
Submitted by: Ralph Meijer <freebsd-gnats2@ralphm.ik.nu>
Approved by: maxim
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
software-generated UUID. Store the result in /etc/hostid and use it in
the future. Perform simple UUID format check, as there is a lot of
hardware with broken UUIDs. The check should be improved to also eliminate
fake UUIDs like 00000000-0000-0000-0000-000000000000.
Requested by: many
|
|
|
|
|
|
|
|
|
|
|
| |
which can be used to turn off multicast pfsync support, and enable
the transmission of directed PFSYNC (IP protocol: 240) packets to
a specific "sync peer" host.
PR: conf/111225
Submitted by: Bas van Beek <bas@tobin.nl>
Approved by: mtm, mlaier
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
UUID and stores it in /etc/hostid ($hostid_file) as well as sets kern.hostuuid
and kern.hostid sysctls on every boot.
Hostid can be reset using '/etc/rc.d/hostid reset' command.
Hostid generation and setting can be turned off by setting variable
hostid_enable to "NO" in /etc/rc.conf.
Reviewed by: mlaier, rink, brooks, rwatson
|
|
|
|
|
| |
Requested by: andre@
MFC after: 1 week
|
| |
|
| |
|
|
|
|
| |
dedicated /boot/ file system and use ZFS for the root file system.
|
| |
|
|
|
|
| |
It'd be nice to send them via e-mail...
|
|
|
|
| |
Submitted by: des
|
|
|
|
|
|
|
| |
Submitted by: des
- When starting mountd(8) and ZFS is enabled, add /etc/zfs/exports file.
- Update rc.conf(5).
|
| |
|
|
|
|
| |
Submitted by: ru
|
|
|
|
|
|
| |
passed to rpc.statd and rpc.lockd
MFC after: 1 week
|
|
|
|
| |
This bug prevents local scripts to start up
|
|
|
|
|
|
|
|
|
|
|
|
| |
and takes over mountcritlocal's role as the early / late divider. This
makes it far easier to add rc scripts which need to run early, such as a
startup script for zfs, which is right around the corner.
This change should be a no-op; I have verified that the only change in
rcorder's output is the insertion of FILESYSTEMS immediately after
mountcritlocal.
MFC after: 3 weeks
|
|
|
|
|
|
|
|
| |
If the firewall script is sourced directly from the script, then any
exit statements in it will also terminate the rc.d script prematurely.
PR: conf/78762
MFC-After: 2 weeks
|
|
|
|
|
|
|
| |
for the sundry other firewalls in the system.
MFC after: 3 days
Submitted by: Richard dot Clayton at cl dot cam dot ac dot uk
|
|
|
|
| |
MFC After: 2 weeks
|
|
|
|
|
|
| |
PR: conf/105465
Submitted By: ru (with minor cosmetic change)
MFC-After: 1 month
|
|
|
|
|
|
| |
if we don't explicitly set the name of the executable program.
PR: conf/104408
|
| |
|
|
|
|
| |
Submitted by: jhb
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All xxx_<ifname> flags are set to empty strings automatically earlier so
eval echo \${${prefix}${_if}${suffix}-${_default}}
not substitute the default but return just the empty string.
Fix it using
eval echo \${${prefix}${_if}${suffix}:-${_default}}
(i.e. treat empty strings as unset)
The bug manifistates itself with the following warning from checkyesno():
/etc/rc.d/dhclient: WARNING: $background_dhclient is not set properly -
see rc.conf(5)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The code looks for all the loaded screensaver modules, tries to
kldunload them, and only loads the new one if kldstat's output shows
that there aren't any left. However, the regexp looking for modules
to unload was still searching according to the the old naming scheme,
splash_<name>.ko, instead of <name>_saver.ko.
MFC after: 3 days
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
insert a slash between ${_chroot} and the pathname if and only if
${_chroot} is set to a non-empty string. Now the pathname is very
likely to be absolute, but we shouldn't take that for granted.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for /tmp and /var. This makes the memory discs swap-backed instead
of malloc-backed. A swap-backed memory disc should not be worse
than a malloc-backed one in any scenario because it will start
touching swap only when needed. OTOH, a malloc-backed disc can
starve limited kernel resources and evenually crash the system.
Reflect the change in the rc.conf(5) manpage. Also stop telling
lies there about softupdates: it does not waste disc space, it
just can delay its freeing.
Suggested by: many
PR: kern/87255
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
Include /var/db/entropy-file in the reseeding if present. It is used for
last-ditch efforts to save entropy and thus should also be used to seed
the RNG when starting. Print a warning instead of an error if writing the
file fails -- err() exits, preventing the umask from being restored.
Also, since there's not much that can be done about it, notifying the user
is all that's needed.
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
ipv6_enable="NO", an IPv4 address is preferred for a
destination address.
MFC after: 1 month
|
|
|
|
|
|
|
| |
and background_dhclient. This allows interfaces who's names are not
valid parts of shell variables and shortens the code.
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
- Update hier(7) to reflect latest changes in mtree file.
- Add UPDATING entry following Intel firmwares inclusion.
Submitted by: mlaier
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
uuencoded format along with their respective LICENSE files.
- Add new share/doc/legal directory to BSD.usr.dist mtree file. This is the
place we install LICENSE files for restricted firmwares.
- Teach firmware(9) and kmod.mk about licensed firmwares. Restricted firmwares
won't load properly unless legal.<name>.license_ack is set to 1, either
via kenv(1) or /boot/loader.conf.
Reviewed by: mlaier, sam
Permitted by: Intel (via Andrew Wilson)
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
arrangement that has no intrinsic internal knowledge of whether devices
it is given are truly multipath devices. As such, this is a simplistic
approach, but still a useful one.
The basic approach is to (at present- this will change soon) use camcontrol
to find likely identical devices and and label the trailing sector of the
first one. This label contains both a full UUID and a name. The name is
what is presented in /dev/multipath, but the UUID is used as a true
distinguishor at g_taste time, thus making sure we don't have chaos
on a shared SAN where everyone names their data multipath as "Fred".
The first of N identical devices (and N *may* be 1!) becomes the active
path until a BIO request is failed with EIO or ENXIO. When this occurs,
the active disk is ripped away and the next in a list is picked to
(retry and) continue with.
During g_taste events new disks that meet the match criteria for existing
multipath geoms get added to the tail end of the list.
Thus, this active/passive setup actually does work for devices which
go away and come back, as do (now) mpt(4) and isp(4) SAN based disks.
There is still a lot to do to improve this- like about 5 of the 12
recommendations I've received about it, but it's been functional enough
for a while that it deserves a broader test base.
Reviewed by: pjd
Sponsored by: IronPort Systems
MFC: 2 months
|
|
|
|
|
|
|
|
|
|
| |
bad or illegal. This prevents matching on systems that
have a name that matches the query.
PR: conf/107560
Submitted by: Christian Laursen <cfsl at pil dot dk>
MFC after: 3 days
Approved by: imp (mentor)
|
|
|
|
|
|
|
|
| |
of the depricated one.
PR: conf/108611
Submitted by: TAOKA Fumiyoshi <fmysh at iijmio-mail dot jp>
Approved by: imp (mentor)
|