Tag Info

New answers tagged

0

Unfortunately, removing a vdev (which this drive is) from a pool is not supported by ZFS currently. The work around would be to dump your data out of the pool and recreate it, then put the data back.


0

FreeBSD divides memory into 5 lists: wired (locked in memory, unpageable) active (recently used) inactive (not recently used) cache free Some of those have minimum free and target free levels, e.g. Pool Minimum Target Free 0.7% 3% Cache 3% 6% Inactive 0% 4.5% (Source: The Design and Implementation of the FreeBSD Operating ...


0

my previous answer doesn't apply freeBSD but i leave it. i tested it and it worked like a charm on debian. for freeBSD you can use following command from sysctl to see if swap is enabled or not: -bash-2.05b$ sysctl vm.swap_enabled vm.swap_enabled: 1 1 - Enabled 0 - Disabled you can disable it with writing following line in /etc/sysctl.conf : ...


0

I don't have enough reputation to comment, so I'll add it as an answer, but a short research pointed out this: Why is swappiness set to 60 by default? which explains in even more details about swappiness And this: https://www.kernel.org/doc/Documentation/sysctl/vm.txt which explains about all vm related parameters. If you're into single process memory ...


3

if you have spare memory increasing memory not working you should change the swappiness parameter. it tells the kernel how often use non physical memory (swap). check swappiness value: cat /proc/sys/vm/swappiness change the swappiness value temporary (lost on reboot) to value 10 (good value that decreases swap usage) sudo sysctl vm.swappiness=10 if you ...


1

ZFS currently has a 255 bytes limit on names. If you decide to use UTF-16 names, you will get a limit of 127 characters. UTF-8, OTOH might encode japanese/korean in 3-byte character, limiting you even further (255/3 = 85). I'm not aware of other concerns, aside from slower indexing of UTF-8 3-byte char strings compared to UTF-16 2-byte char strings. So - if ...


0

I think the easiest would be to use a transparent HTTP proxy (like squid) which logs the requests. Redirect all outgoing HTTP requests to that server. To get the MAC-Adress either correlate with the DHCP servers lease file or use something like arpwatch, if the users assign the IPs themselves.


3

Is your question whether LibreSSL is intended to be a drop-in replacement for OpenSSL? If so, yes. This is explicitly the intention stated by the developers. One point of the current release is to ensure that goal by letting the people responsible for binary packages and source repositories test it. There are a few problems still, but most of them are minor: ...


1

From what I see they have not changed the library and binary names. So every port that sets USE_OPENSSL should also work with libressl if you define WITH_OPENSSL_PORT in your make.conf Binary packages will still use the base system's openssl.


0

Why does *BSD uses driver specific names for network interfaces? To make things simple. If you look to an interface named bge0 and take a look at the manuals or use your mnemonic link system you will quickly remember that this driver is a Broadcom Gigabit Etherhet. This document is also usefull. Does it mean there is no abstraction layer describing ...


0

Try going to: /boot/kernel and loading: kldload geom_sunlabel.ko Check if labels showed up. If they didn't you're unlikely to be able to access them (easily) Long time ago I made it work: http://marc.info/?l=freebsd-bugs&m=110942523517592&w=4 But soon after that I removed Solaris and never came back to it. FreeBSD disk infrastructure is ...


1

FreeBSD always includes a compiler, so there is no "build essential" type package.


2

No matter the fancy name used here, both are solutions to a specific problem: A better segregation solution than classic Unix chroot. Operating system-level virtualization, containers, zones, or even "chroot with steriods" are names or commercial titles that defines the same concept of userspace separation, but with different features. Chroot was introduced ...


0

All points out to be a bug/regression that started at FreeBSD 9.1 kern/173435 And sadly, there is no workaround available. Maybe you could give more details of your issue(hardware, FreeBSD version) on kern/173435.


0

Another option would be to use geli block device encryption on a file mounted as a disk via the md driver using a vnode backing.


2

It's caused by the process exiting between top getting the process list and top trying to get info on that particular process. It's more common on a very busy box but generally safe to ignore. You might consider it a bug, you might not.


0

pkg install mod_php5 should take care of it.



Top 50 recent answers are included