[Bug 224157] sysutils/moosefs3-master: Update to 3.0.99
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Dec 7 03:26:46 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224157
Bug ID: 224157
Summary: sysutils/moosefs3-master: Update to 3.0.99
Product: Ports & Packages
Version: Latest
Hardware: Any
URL: https://moosefs.com
OS: Any
Status: New
Keywords: easy, patch, patch-ready
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: freebsd at moosefs.com
CC: lifanov at freebsd.org
Attachment #188606 maintainer-approval+
Flags:
Created attachment 188606
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188606&action=edit
Update to the latest stable version (3.0.99-1)
This is a small change in ports and passes QA (portlint, poudriere).
Recent changes since MooseFS 3.0.97:
* MooseFS 3.0.99-1 (2017-11-23)
- (master) disconnect all clients when exports has changed
- (mount) do not show message about 'negative travel time' when the measured
time is zero (happens in virtual machines)
- (all) fixed get16bit function on big-endian machines
* MooseFS 3.0.98-1 (2017-10-12)
- (mount) changed default cache mode on OS X from 'direct' to 'auto' due to
problems with mmap
- (cgiserv) added seteuid to 'mfs' or 'nobody'
- (cs+tools) use readdir instead of readdir_r on glibc 2.24+
- (debian) added support for systemd in debian packages
- (all) fixed library dependencies (for libpcap,libz and libm)
- (mount) fixed race between defered 'open' and 'locks'
- (master) more chunk debugs and better handling chunk status change
- (cs) fixed handling mark for removal (after reload sometimes cs could send
chunks marked for removal as normal chunks)
- (master) added file with metadata checksums (for future use)
- (master) fixed way of sending gids to changelog/follower
- (master) added inode checksum for some changes sent to changelog/follower
- (metadump) added '0x' prefix for fileds dumped as hex numbers
- (master) fixed ACL mask synchronization issues (restoring from
changelog/leader->follower)
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list