[DGD] Using a shell script as a hotboot stub
Raymond Jennings
shentino at gmail.com
Tue Mar 28 05:25:41 CEST 2017
Managing the juggle of snapshots and incremental snapshots, while at
the same time dealing with the fixed parameters of the "hotboot"
parameter in the config file, prompted me to try using a small shell
script as a stub.
Basically, it does an inspection of the snapshots that are found
around and uses that to choose what arguments to pass onto dgd.
Thankfully, it seemed to work flawlessly and the client end couldn't
even tell that the server had bounced through a script before
re-exec'ing dgd.
The "dangling connections" that the previous run left behind for the
new dgd seem to have been left completely unmolested by the shell
scripting process in the middle
Any problems with this idea? Particularly ones that a test like this
would NOT reveal?
More information about the DGD
mailing list