Search results

10.2-RELEASE was tagged from releng/10.2 at SVN r286666. It would have been too soon to have had this fix.

I added the 'with base Sendmail' in the title after moving the thread but the text did say Sendmail. Mwh65, were you able to get the source needed to execute those steps? The src.txz won't contain all the patches applied via freebsd-update but is a viable method of getting the source...

If you are asking with regards to official errata you can apply via freebsd-update, then no, there hasn't been any errata issued for this particular issue (See https://www.FreeBSD.org/security/notices.html).

lme@ is right. I didn't think of that. Having various versions of userland is how ports-mgmt/poudriere compiles packages against different releases of FreeBSD. Unless something on ARM doesn't behave properly, the new 11.0-CURRENT base system and kernel should be able to run userland...

Here or the ports@FreeBSD.org mailing list are both fine for questions like this. However, if you were going to ask to have a committer look at changing a port then ports@FreeBSD.org is the way to go since there are many more ports committers that keep an eye on that mailing list.

There is an open PR for setting 9.4 as the default version: 201796

Strange. I built it with Ruby 2.1 just fine. Then I noticed you are using 2.2 and I built it with the 2.2.4 that is in ports as of today. I also built it with DEBUG and SYMLINK enabled for www/rubygem-passenger but I did not customize www/nginx past the PASSENGER option. Can you make...

You did try service mountd reload after the NTFS mountpoint was available, correct? If that didn't work then it could certainly have to do with where nfsd acts to service requests to the file system. Samba is just a userland application and works a bit differently.

I'm not sure if it being a order of operations type situation with a FUSE mount has anything to do with this. What happens if you service mountd reload after the system is fully up and running? Does that change anything?

It's still $DISPLAY. What shell are you using and what is the exact error you see? If you are using the default tcsh then the syntax is setenv DISPLAY :0. If you are using a Bourne like shell then the syntax you had earlier is correct.

From the looks of things poking around on http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/, it seems the ARM platform only has ISO images. So you'll have to use the compiling method of creating a jail.

Can you post the following? cd /usr/ports/www/nginx; make showconfig and cd /usr/ports/www/rubygem-passenger; make showconfig

8015836945 bytes / 2723102 packets = 2943.64. I'm guessing your NIC supports TSO since the standard would be a 1500 byte packet. ifconfig <interface> -tso will likely make the results match your expectations but TSO can be left active if it doesn't interfere with anything as it will save some...

In short, don't. The synproxy option should only be used under specific situations, such as when you are under an active DDoS. It shouldn't be used normally. Just do 'keep state' or leave it off all together as 'keep state' is implied.

What does zpool status -v show?

If you only have to serve files then NFS would work. If you are using iSCSI to present a raw block device for another operating system to have its own file system on that that of course is another story. Also a ZFS pool is just a bunch of disks. You create a ZFS pool but then it's the ZFS...

Conceptually yes. A full send/receive of the initial snapshot would provide a basis for doing incremental snapshots of just what has changed afterwards. The handbook has some good information on the topic of using zfs send and receive for snapshots to get you started. Snapshots can also be...

From the looks of things there is a mix and match of PHP compiled with the ZTS option set to on and not. How exactly did you fix it for future folks looking at this thread? And for future reference you can also set solved yourself ("Thread tools" at the top right, "edit thread", add "solved" tag).

Indeed. I didn't look closely and assumed by your verbiage you were the original poster. I'll leave that to eatonphil to clarify if everything that was needed was answered.

I've never used WordPress but is the WordPress FTP feature a standard thing as part of Wordpress 4.4? If so it would be worth taking a few minutes to open a PR at https://bugs.FreeBSD.org/bugzilla/ against the www/wordpress port asking for the ftp/php56-ftp to be listed as a dependency. A few...