Tag Info

Hot answers tagged

6

ZFS pool information is not stored in a plain text file. Information about a pool is stored on the disks themselves. ZFS pool information can also be written to a ZFS cache file, but it does not contain mount point information. If you want to get mount point values for your ZFS pools you can use the following: zfs get mountpoint <pool name> zfs get ...


4

As Gene points out, the list of file systems (not partitions!) in a ZFS pool is stored within the pool itself. Specifically, it is stored as a part of the pool metadata, which is not easily accessible in raw form. You can access the metadata using zdb (the ZFS debugger tool), but you need to be careful as well as have some familiarity with the ZFS on-disk ...


3

According to Mozilla, this configuration should work: <VirtualHost *:443> ... SSLProtocol all -SSLv2 -SSLv3 ... </VirtualHost>


2

@MichaelHampton & @ChrisS is right: This cannot be done as /usr/local/libexec/apache24/mod_ssl.so linked against older version of openssl /usr/lib/libssl.so.6. [root@alexus ~]# ldd /usr/local/libexec/apache24/mod_ssl.so /usr/local/libexec/apache24/mod_ssl.so: libssl.so.6 => /usr/lib/libssl.so.6 (0x801236000) libcrypto.so.6 => ...


1

Unless you've specified a custom bootstrap template this is what bootstrap is trying to run. At the very least it expects both bash and either wget or curl to be installed, and findable via PATH. It's been awhile since I've used FreeBSD, but I remember that none of those things were included in a default install last time I did one. I've recently said some ...


1

Which Kerberos are you using here? The built-in one or security/krb5 from MIT? When installing sssd, it requires that security/krb5 be installed which at this moment is still considered experimental in FreeBSD. Thus this question. I am not having any luck getting the AD users/groups when executing 'getent' commands. it might be due to the fact that the ...


1

try this: export HISTTIMEFORMAT="%Y-%m-%d %T " export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p user.info -t "bash[$$]" "($USER) $line"; done); trap 1 2 15;' this does the logging AND it prevents logging of timestamps that are used for the bash ...



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