Tag Info

Hot answers tagged

2

Even though the question is more than half a year old, since I just had the same problem Don't configure your IP address on the physical member interfaces of the bridge but the bridge interface itself. This is mentioned in the FreeBSD handbooks section on bridging. My understanding is that this is due to the way the packets are processed. if_bridge(4) ...


2

No. Don't do it. Any form of backup that revolves around intentionally failing an array or pool of disks is fraught and irresponsible. If you could provide details about your rsync command line, what you're transferring, the connection between the servers and any other specifics, we may be able to help with a more robust solution.


2

I have figured this out thanks to @citrin's comment. Adam Weinberger reported this as a bug here. He also provided two patches for two different desirable options: pre-building the man pages, or building cmake without them. I opted for the latter one. The attachment here includes little fixes to the Makefile and pkg-plist of the corresponding port. I just ...


1

Just a very wild shot in the dark; netatalk documentation tells this: The AFP protocol mostly refers to files and directories by ID and not by name. Netatalk needs a way to store these ID's in a persistent way, to achieve this several different CNID backends are available. The CNID Databases are by default located in the ...


1

The TERM environment variable probably won't be enough, because we are talking not about the cursor moving maneuvers, but about the command line editing tool. You need to set up in your command line editing library, which command can enable the cursor moving in the different directions. Your shell is probably bash, which uses the readline library for ...


1

Have a look in /etc/termcap or /etc/terminfo (not sure which one FreeBSD uses) if there is a termcap entry for xterm-256color. If yes, it is probably wrong (or whatever program you are in is not correctly using the terminal information but trying to parse terminal codes manually; if you have a version of GNU Bash on your FreeBSD, try starting this one and ...


1

FreeBSD limits the length of mount point names to 88 chars. The reasons for this are somewhat esoteric, but has to do with aligning a memory structure on page boundaries[1]. You can patch the mount binary to use a larger limit or to remove it all together[2] but this may cause crashes. I have successfully removed the check (also for vagrant with nfs) and ...


1

Impossible to say what happened during your install without more info which at this point is probably not available. In theory, even if your HW RAID was enabled and therefore the OS only saw 1 physical disk, you should still be able to put ZFS on that, though it would be a bad idea. It's always better to disable the hardware RAID when using ZFS. You should ...


1

If you can't use single user due to ACPI, use the interactive boot loader option to disable ACPI, then add hint.acpi.0.disabled=1 to /boot/loader.conf as the previous answer suggested.


1

1) This is not the handbook, this is a man page for acpi. 2) You could disable the entire ACPI, add hint.acpi.0.disabled=1 to the /boot/loader.conf and reboot.


1

Using ZFS + VMware + NFS is a terrible idea. It will get you the worst result. Vmware uses an implementation of NFS that need constantly to do SYNCed writes, and wait for each one to do so. And this is extremely slow on ZFS.. ZFS first writes in the ZIL log and a lot latter do the actual wirte on disks (and only then confirm the sync write). I got 5MB/s on ...


1

As told above, try first: # setenforce 0 if the files appear, then it's a SELinux missing context. Enable SELinux again, then add context to folder: # setenforce 1 # chcon -Rt samba_share_t /usr/share/nginx/www/


1

#1) Chrooting virtual hosts individually is not supported. The "Context" for the ChrootDir directive is "server config," and thus... "This means that the directive may be used in the server configuration files (e.g., httpd.conf), but not within any <VirtualHost> or <Directory> containers. It is not allowed in .htaccess files at all." [1] It is ...



Only top voted, non community-wiki answers of a minimum length are eligible