On 15.10.15 10:47, madams9 wrote:
> Consequently, I'm setting Monit to tell me whether the process is running or
> not and that's it. This seems okay for now, but I continue to look into
> finding a way to test these things to determine whether they are running and
> at least sending an alert.
>
On 10/12/2015 5:24 PM, Carl Wilhelm Soderstrom wrote:
> On 10/12 09:41 , Holger Parplies wrote:
>>> Hmm, the stock monitrc file provides the following suggestion among others:
>>> #if failed url http://user:passw...@www.foo.bar:8080/?querystring
>>> # and content == 'action="j_security_ch
On 10/12 09:41 , Holger Parplies wrote:
> > Hmm, the stock monitrc file provides the following suggestion among others:
> > #if failed url http://user:passw...@www.foo.bar:8080/?querystring
> > # and content == 'action="j_security_check"'
> >
> > So perhaps monit could log into the Backu
n "the one full backup
that will be kept for ages contains only the first few files").
All of that said, there might be valid reasons for sticking to the wireless
connection, and my points may be non-issues for you.
> [...]
Carl Wilhelm Soderstrom wrote on 2015-10-12 12:00:12 -0400 [
On 10/11 03:28 , madams9 wrote:
> ## BACKUP PC
> check process backuppc with pidfile "/var/log/backuppc/BackupPC.pid"
> start program "/usr/sbin/service backuppc start"
> stop program "/usr/sbin/service backuppc stop"
> if failed host adamsmdk port 16073 proto http then restart # change if not
> l
