I am wondering if it makes sense to rename the script to something like
"snapshot-script-generator" because
1. "safe" is a bit too strong here
2. the script does not take snapshot but generate a script that takes
snapshot.


On Mon, Jun 2, 2014 at 10:24 AM, Jeremy Edwards <notifications@github.com>
wrote:

> In google-startup-scripts/usr/share/google/safe-snapshot-for-non-boot-disk:
>
> > +################################################################################
> > +# This script is freely inspired by this great article by F. Voznika: [1].
> > +#
> > +# It tries to take a snapshot from a live VM by stopping the services that most
> > +# likely impact its disk usage. Please remember that a safe bit-a-bit copy of a
> > +# disk is guaranteed only on an unattached disk (or disk attached to a VM which
> > +# is not in state RUNNING).
> > +#
> > +# To give you full control, it just outputs what it would do, so you can cut/paste
> > +# and maybe add additional scripts to the naive "service start/stop" provided here.
> > +#
> > +# Note that so far the '/' is prohibited, as this would require part of the code to
> > +# be executed on another machine (freezing I/O on root disk makes the VM unusable
> > +# until a reboot is issued)
> > +#
> > +# *** ACHTUNG *** THIS SCRIPT IS PROVIDED AS IS. USE AT YOUR OWN RISK.
>
> s/ACHTUNG/WARNING/
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleCloudPlatform/compute-image-packages/pull/71/files#r13296142>
> .
>