Strange periodic problem
Adam Vande More
amvandemore at gmail.com
Tue Oct 24 04:02:56 UTC 2017
On Mon, Oct 23, 2017 at 9:51 PM, Paul Schmehl <pschmehl_lists at tx.rr.com>
> I wrote a script to do database backups. It worked well, so I copied it to
> another server. I had to alter it, because the db was too big to send
> through email, so it creates the backup, removes the previous days and then
> sends email to me notifying me that it ran. Except, it doesn't work.
> And I have no idea why.
> The periodic script is executable.
> # ls -lsa /etc/periodic/daily/220.dbbackup
> 2 -rwxr-xr-x 1 root wheel 37 Oct 19 12:31 /etc/periodic/daily/220.dbback
> The script calls sh to run the actual script.
> # cat /etc/periodic/daily/220.dbbackup
> Periodic.conf enables the script.
> # grep dbbackup /etc/periodic.conf
> The script itself is executable.
> # ls -lsa /usr/local/bin/dbbackup.sh
> 2 -rwxr-xr-x 1 root wheel 446 Oct 11 23:40 /usr/local/bin/dbbackup.sh
> The script runs manually, and I get the email.
> # /usr/local/bin/dbbackup.sh
> rm: /usr/home/pauls/102217.alldb.sql: No such file or directory
> (The previous backup doesn't exist, because the script isn't running
> What have I missed?
Does the cron log indicate entry ran?
More information about the freebsd-questions