From 5789fbd7d7fd8031d0f4d8eba3a6d586d44cc8b7 Mon Sep 17 00:00:00 2001 From: Jim Salter Date: Mon, 4 Jul 2016 16:29:09 -0400 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d77a627..6394cd4 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ Want an example? Watch a short real time demo of rolling back a full-scale cryptomalware infection in seconds: -[![Sanoid rollback demo](http://openoid.net/sanoid-video-launcher.png)](https://youtu.be/ZgowLNBsu00 "Sanoid rollback demo") +[![Sanoid rollback demo](http://www.openoid.net/sanoid_video_launcher.png)](https://youtu.be/ZgowLNBsu00 "Sanoid rollback demo") More prosaically, you can use Sanoid to create, automatically thin, and monitor snapshots and pool health from a single eminently human-readable TOML config file at /etc/sanoid/sanoid.conf. (Sanoid also requires a "defaults" file located at /etc/sanoid/sanoid.defaults.conf, which is not user-editable.) A typical Sanoid system would have a single cron job: