Installer test: Give the webserver more memory

Otherwise its unionfs may run into allocation failures.

http://hydra.nixos.org/build/5508805
Bump the amount of memory for VirtualBox image generation

http://hydra.nixos.org/build/5509519
Give the webserver in the installer test still more memory

http://hydra.nixos.org/build/5510269
mysql/mysql55: Log to stderr instead of logfile.

This should integrate the logging more tightly into systemd, so for
example "systemctl status mysql" actually gives an overview about what's
actually going on.

This removes the logError option attribute, so in case you still want to
write into a logfile, I've introduced an option called extraOptions, so
you can use something like:

services.mysql*.extraOptions = ''
  log-error = /var/log/mysql_err.log
'';

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
postgresql: Log to stderr by default.

Now systemctl status will properly pick up the right logs.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
postgresql: Add initialScript for initial SQL.

Just like in the MySQL service module it really makes sense to provide a
way to inject SQL on the first start of the database cluster.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
postgresql: Allow to specify recoveryConfig.

This is needed for streaming replication in PostgreSQL 9.0 and higher.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Use "or"
nixos-rebuild: Support Nix's --repair flag
wpa_supplicant: Fix wlan interface detection on Linux 3.4

Linux 3.4 apparently doesn't have the "wireless" file.
Initial wireless configuration docs
don't try to re-import pools on service change

When nixos-rebuild grabs a new kernel, it will build new spl/zfs
modules, which will change the service. On completion nixos will try and
restart the services which will try and import pools again, and
generally will fail.

The pools are already imported, we don't need to do it again..
calling zfs mount -a again doesn't make sense
NFS: Use network-online.target instead of remote-fs-pre.target

Turns out that remote-fs-pre.target is not actually "wanted" anywhere,
so statd is not started before remote filesystems are mounted.  But
remote filesystems do "want" network-online.target, so we can use that
to pull in statd and idmapd.

Not sure if this is really the right thing to do, but it works for
now.  Background:

  https://bugzilla.redhat.com/show_bug.cgi?id=787314

http://hydra.nixos.org/build/5542230
Start sm-notify/statd atfer nfsd

The README of nfs-utils explains that we must not notify clients
before nfsd is running, otherwise they may fail to reclaim their
locks.  OTOH it's allowed but not required to start "rpc.statd
--no-notify" before nfsd.  So for simplicity we do both after starting
nfsd.
Don't pull in the old qemu-kvm
NFS test: Set a fixed fsid

Otherwise clients get a "Stale NFS handle" error after the server
reboots.  Not clear why this is the case, since the fsid shouldn't
change across reboots...
Add a test for NFSv4

However it currently fails because locking seems to be broken with
NFSv4.
Disable the installer.swraid test

This fails randomly for unknown reasons,
e.g. http://hydra.nixos.org/build/5542510.
Work around "Input/output error" opening /dev/ttyS0

E.g. http://hydra.nixos.org/build/5541847

This is a random occurence, maybe due to a race with something else.
So just retry until it works.