Jarkko Ypäjä wrote: > Hi again, > > I still seem to have some problems running backup from multipe servers > at once.
Actually it sounds more like you have a problem running dirvish from cron, which is a somewhat different problem. > > and here's my crontab -e > 10 22 * * * dirvish-expire --vault server1/backupu/root > 30 22 * * * dirvish-expire --vault server1/root > 45 22 * * * dirvish-expire --vault server2/backupu/root > 0 23 * * * dirvish-expire --vault server2/root > 0 1 * * * dirvish --vault server2/backupu/root > 0 1 * * * dirvish --vault server1/backupu/root > 0 3 * * * dirvish --vault server2/root > 0 4 * * * dirvish --vault server1/root > > The default.conf should be correct. > > Now, for some reason when I do the command manually(for example dirvish > --vault server1/backupu/root it starts running without any problems. For > some reason the command executed via cron does not start at all. I can > see from the syslog that the command has been started but it doesn't > keep running. What output do you get from the dirvish jobs run from cron? Or you could just skip ahead :-) and make sure that the value of PATH when you do your manual tests matches the value of PATH used by cron. I strongly suspect you'll see the same error. Then either wrap dirvish in a shell script which sets PATH (you're probably missing /usr/local/sbin) or set it in your crontab, mileage depending on what else you have in your crontab, etc., etc. --Jon Radel
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
