Date: Sat, 23 Jun 2012 19:50:32 +0200 (CEST) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Chad Perrin <perrin@apotheon.com> Cc: freebsd-questions@freebsd.org Subject: Re: backup tools Message-ID: <alpine.BSF.2.00.1206231948410.40095@wojtek.tensor.gdynia.pl> In-Reply-To: <20120623164614.GA13602@hemlock.hydra> References: <20120622160903.GE24912@hemlock.hydra> <20120622184740.GA67847@slackbox.erewhon.net> <20120623003717.GD7876@hemlock.hydra> <20120623075928.GA19093@slackbox.erewhon.net> <alpine.BSF.2.00.1206231007190.31324@wojtek.tensor.gdynia.pl> <20120623125739.GA82828@jorge.cc> <alpine.BSF.2.00.1206231512210.38324@wojtek.tensor.gdynia.pl> <20120623134602.GA36552@jorge.cc> <20120623164614.GA13602@hemlock.hydra>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Actually, a Wake-On-LAN feature is not at all necessary for me in this > case. It's a simple enough task to just trigger a backup manually at the > command line via a script that automates the process. still. a separate wol tool is available in ports. You may easily construct shell script that will execute it, wait a bit, check out if server booted with ping, then wait a bit more (so inetd or rsyncd started) then run rsync. Unix philosophy means have one program to do think well, not to do everything. This is what make me an exclusive unix "fanatics".
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1206231948410.40095>