different servers.

enough and better then nothing (which is what happens now).

There are still a couple of other places this needs to be done.

This is needed in the WITHZFS && !WITHAMD case where ZFS handles the
HUPing of mountd but we still need to generate the valid mount list
for autofs on boss.

to resource shortage.

since those vlans might not be consistent in the DB. In general, we
need to be looking at only actual experiments with vlans on the
Experiment stack, but this change fixes the problem with ptopgen
bailing early with an error.

split into two separate apache servers, one for the web interface and
another for all the geni RPC ports. Shot in the dark, we are out of ideas.

intended to finish, but never did. Unfortunate since we have lost some info
that might have been useful.

In addition, we now record provenance on a plain profile copy, in addition
to a clone.

Fixes to the profile history display, and add a new pointer to the profile
derived from when it is not null.

Also add sitevar for PhantomNet portal banner message.

extension history, All buttons disabled/hidden.

use SHA265 ($5$) with a 16 character random salt from /dev/urandom.
Enabled for Utah MS for now, will push out to other clusters if no
problems over the next week.

It assumed addresses were unused if node_id was NULL.  This used to be
true before the introduction of per-experiment dynamic address pools (when
public addresses were mapped one-to-one with VMs).  Unfortunately this
code was not updated when experiment address pools were added, and so
it would have permitted the deletion of currently assigned addresses.

So, the scripts are now in clientside/tmcc/linux since they're the same
for any systemd-based Linux, and the centos7 and ubuntu15 makefiles
install those files.

Also had to improve fixup-fstab-swaps to handle the case where the / is
something like /dev/disk/by-uuid/<UUID> which is a symlink to the real
dev.  So try readlink -f to handle that.

changes and some checks to prevent a user from instantiating a disabled
version.

waiting till it finished setting up (or fails). This is really nice when a
1000 node experiment has gone awry and it is pointless to wait for it to
finish. When we do this, we mark the instance as canceled in the DB, and
then wait for create_instance() to notice it. When it does, it stops
waiting and invokes terminate with a new cancel option at the backend.

through the loop we look to see if signals are pending, and if so we return
early with an error. The caller (libvnode_xen) can use this to avoid really
long waits, when the server has said to stop what its doing. For example, a
vnode setup is waiting for an image lock, but the server comes along ands
to stop setting up. Previously, we would wait for the lock, now we return
early. This is to help with cancelation where it is nice if the server can
stop a CreateSliver() in its tracks, when it is safe to do so.

cancel option, will stop a CreateSliver() in its tracks. We stop the
monitor, then cleanup the slice. I also added an optimization for tearing
down large numbers of VMs on shared nodes, previously we were doing them
one at a time. Note that only the Portal is going to use this option, since
it loosely depends on code in the XEN clientside (described in another
commit).

Also, sync up a couple of files with 10.2.