If you're going to upgrade your existing ZFS pool drives from 512/512e sector size (ashift=9) to newer AF/4k drives (ashift=12) you'd be better off creating a new pool with ashift=12 and using zfs send recv to populate the new pool with your data.

If you are researching prior to creating any pool, force ashift=12 during pool creation, even if you're using 512/e drives by using zpool create -o ashift=12 yourtank /dev/drive1 /dev/drive2 ...etc This will 'future-proof' your ZFS pool.

You may receive a similar error in FreeNAS:
"nas manage.py: [middleware.exceptions:38] [MiddlewareError: Disk replacement failed: "cannot replace (driveID) with gptid/(gptID): devices have different sector alignment, "

To check your current ashift value, use:
zdb -C | grep ashift

ashift: 9 = 2^9 = 512bytes (bad)
ashift: 12 = 2^12 = 4096bytes (good)

If you absolutely can't do that, these two sysctls allow you to use 4k drives as if they're 512/e. There is a significant performance hit if you do this.

Sysctls:
Set these sysctls via ssh or using the Sysctl UI underneath 'System' in the FreeNAS web interface.
vfs.zfs.vdev.larger_ashift_disable=1
vfs.zfs.vdev.larger_ashift_minimal=0

Then you should be able to offline/replace/resilver a 4k drive into your 512/e pool. Personally my throughput greatly increased despite ashift=9, but I moved my ZFS pool from 6x2TB 5400RPM to 6x2TB 7200RPM. Again, the right way to do this is to use ashift=12 with 4k drives.

crit?: 0

Disregard the bullshit 'goto menu' line in the official Fog wiki for advanced pxe boot. Use 'boot' instead.

:foobar
initrd http://${fog-ip}/ISO/foobar.ISO
chain memdisk iso raw ||
goto MENU

change to

:foobar
initrd http://${fog-ip}/ISO/foobar.ISO
kernel http://${fog-ip}/fog/service/ipxe/memdisk iso raw ||
boot

I wasted hours on that.

crit?: 0

If you're connecting a CLI Synergy client to a GUI Synergy server, the password to feed synergyc isn't the password you defined on the server. It is an MD5 hash of that password. See here.

crit?: 16

If create and activate a new wordpress child theme, you may notice your ul/li menu div and class go haywire. You'll need to go to appearance>menus and then tick 'primary navigation' for whichever menu is your primary navigation. So stupid.

crit?: 0

When creating a zabbix_agentd.conf for windows/linux hosts rollout, instead of manually specifying the Hostname=Foo line, comment that line and uncomment HostnameItem=system.hostname

Then you can proceed to defining discovery of zabbix agents, and actions to add the hosts to their respective groups and templates.

So much easier.

crit?: 0

Warning, make a backup of /tftpboot/pxelinux.cfg/default before doing any of this. It will replace without prompting, wiping out any custom ISOs.

With Fog 0.32 if you attempt to use Quick Image, you will be prompted for a password. Log in to the management interface, Other Information, PXE BootMenu to create the PXE Menu and set the fog.quickimage password. Make sure to use a password 4 chars or longer.

PXE Menu: http://X.X.X.X/fog/management/index.php?node=about&sub=pxemenu

After you get past that point, you'll encounter: "Enter a valid FOG username and password"

Your normal user/pass may fail silently if the password is less than 3 characters, for instance 'fog'. Log into management interface, User Management, click the user (fog) and set a password 4 chars or longer.

Users: http://X.X.X.X/fog/management/index.php?node=users

crit?: 0

When using greylistd with exim4, you may add a line to skip or bypass greylisting for recipients as maintained in local plaintext file using one email address per line. Basically this says greylist the triplet unless recipient is in the list.

Create recipient whitelist, one address per line:
/etc/greylistd/whitelist-recipient

Backup existing conf file if multi-file config:
cp /etc/exim4/conf.d/acl/30_exim4-config_check_rcpt ~/
or
cp /etc/exim4/exim4.conf.template ~/

Edit the acl portion of multi file conf:
vim /etc/exim4/conf.d/acl/30_exim4-config_check_rcpt

Modify:
defer

message        = $sender_host_address is not yet authorized to deliver \
mail from <$sender_address> to <$local_part@$domain>. \
Please try later.
log_message = greylisted.
!senders = :
!hosts = : +relay_from_hosts : \
${if exists {/etc/greylistd/whitelist-hosts}\
{/etc/greylistd/whitelist-hosts}{}} : \
${if exists {/var/lib/greylistd/whitelist-hosts}\
{/var/lib/greylistd/whitelist-hosts}{}}
!authenticated = *
!acl = acl_local_deny_exceptions
domains = +local_domains : +relay_to_domains
verify = recipient
condition = ${readsocket{/var/run/greylistd/socket}\
{--grey \
${mask:$sender_host_address/24} \
$sender_address \
$local_part@$domain}\
{5s}{}{false}}

To:

defer
message = $sender_host_address is not yet authorized to deliver \
mail from <$sender_address> to <$local_part@$domain>. \
Please try later.
log_message = greylisted.
!recipients = /etc/greylistd/whitelist-recipient
!senders = :
!hosts = : +relay_from_hosts : \
${if exists {/etc/greylistd/whitelist-hosts}\
{/etc/greylistd/whitelist-hosts}{}} : \
${if exists {/var/lib/greylistd/whitelist-hosts}\
{/var/lib/greylistd/whitelist-hosts}{}}
!authenticated = *
!acl = acl_local_deny_exceptions
domains = +local_domains : +relay_to_domains
verify = recipient
condition = ${readsocket{/var/run/greylistd/socket}\
{--grey \
${mask:$sender_host_address/24} \
$sender_address \
$local_part@$domain}\
{5s}{}{false}}

Update Exim4 conf file
update-exim4.conf

Restart Exim4
/etc/init.d/exim4 restart

crit?: 0

To make Galleria Classic theme have a 'fullscreen' toggle in the upper right hand corner of the gallery stage (replace all brackets "[]" with angle brackets "<>":

1. Add this div to your main styles-sites.css (adjust position/top/right as necessary) to style a fullscreen link in the top right of the galleria stage:
#fs {
position: relative;
top: 30px;
right: 20px;
text-align: right;
color: #ccc;
font: italic 11px/1 arial,sans-serif;
z-index: 2;
}
#fs a:hover,a.fs:active {color:#fff; background: none;}

2. Add this to your page before you call the galleria to add a "fullscreen" link in the top right of the galleria stage:

[div id="fs"][a id="fullscreen"]fullscreen[/a][/div]

3. Add this to your galleria.ready function to enable fullscreen toggle:

$('#fullscreen').click(function() {
gallery.toggleFullscreen(); // toggles the fullscreen

4. so your full galleria script will look like:

[script type="text/javascript"]
Galleria.loadTheme('galleria/themes/classic/galleria.classic.min.js');
Galleria.configure({
});
Galleria.run('#galleria');
Galleria.ready(function() {
var gallery = this; // galleria is ready and the gallery is assigned
$('#fullscreen').click(function() {
gallery.toggleFullscreen(); // toggles the fullscreen
});
});
[/script]

crit?: 0