I just installed dirvish (all machines are freebsd 6 except for one that is freebsd 5)
It all runs spiffily from the command line (using 'sudo' or from a root shell via 'sudo su root' first) However whenever it is run from cron it acts like a dry-run is being done: ie: no actions are taken. I have not delved in to the scripts yet, I was hoping someone here could point out the stupid thing I was doing that caused it to behave like this. The biggest hint is the output from cron looks like: 04:30:01 dirvish --vault kamidake-root --image-time "23:59" 04:30:01 dirvish --vault kamidake-usr-local --image-time "23:59" 04:30:01 dirvish --vault old-kamidake-root --image-time "23:59" 04:30:01 dirvish --vault old-kamidake-usr-local --image-time "23:59" 04:30:01 dirvish --vault azaka-root --image-time "23:59" 04:30:01 dirvish --vault azaka-usr-local --image-time "23:59" 04:30:01 dirvish --vault matsubue-root --image-time "23:59" 04:30:01 dirvish --vault matsubue-usr-local --image-time "23:59" 04:30:01 dirvish --vault motoko-root --image-time "23:59" 04:30:01 dirvish --vault motoko-usr-local --image-time "23:59" 04:30:01 dirvish --vault fatora-root --image-time "23:59" 04:30:01 dirvish --vault fatora-usr-local --image-time "23:59" 04:30:01 dirvish --vault fatora-var-log --image-time "23:59" 04:30:01 dirvish --vault lockers00 --image-time "23:59" 04:30:01 dirvish --vault lockers01 --image-time "23:59" 04:30:01 dirvish --vault lockers02 --image-time "23:59" 04:30:01 dirvish --vault lockers03 --image-time "23:59" 04:30:01 dirvish --vault homes00 --image-time "23:59" 04:30:01 dirvish --vault homes01 --image-time "23:59" 04:30:01 dirvish --vault homes02 --image-time "23:59" 04:30:01 done Note, all the jobs take no timme to finish. There is no new image directory in each of the vaults. If I then run dirvish from a command line via sudo it looks like: 07:51:59 dirvish --vault kamidake-root --image-time "23:59" 07:52:00 dirvish --vault kamidake-usr-local --image-time "23:59" 07:52:18 dirvish --vault old-kamidake-root --image-time "23:59" 07:52:20 dirvish --vault old-kamidake-usr-local --image-time "23:59" 07:52:47 dirvish --vault azaka-root --image-time "23:59" 07:52:48 dirvish --vault azaka-usr-local --image-time "23:59" 07:52:50 dirvish --vault matsubue-root --image-time "23:59" 07:52:51 dirvish --vault matsubue-usr-local --image-time "23:59" 07:53:00 dirvish --vault motoko-root --image-time "23:59" 07:53:02 dirvish --vault motoko-usr-local --image-time "23:59" 07:53:03 dirvish --vault fatora-root --image-time "23:59" 07:53:05 dirvish --vault fatora-usr-local --image-time "23:59" 07:53:06 dirvish --vault fatora-var-log --image-time "23:59" 07:53:12 dirvish --vault lockers00 --image-time "23:59" 07:53:19 dirvish --vault lockers01 --image-time "23:59" 07:53:35 dirvish --vault lockers02 --image-time "23:59" 07:53:47 dirvish --vault lockers03 --image-time "23:59" 07:54:27 dirvish --vault homes00 --image-time "23:59" 07:59:21 dirvish --vault homes01 --image-time "23:59" 08:00:45 dirvish --vault homes02 --image-time "23:59" 08:01:41 done (notices it actually took time to do all these runs, and the new image dirs exist.) The cron command is: 30 4 * * * /usr/local/sbin/dirvish-expire --config /usr/local/etc/dirvish/master.conf ; /usr/local/sbin/dirvish-runall --config /usr/local/etc/dirvish/master.conf | mail -s "Dirvish output" scanner I put the explicit "--config" in there just to be sure it was getting the right config (which by default on freebsd ports installs is /usr/local/etc/dirvish/master.conf.) Any immediate ideas? --Scanner ([EMAIL PROTECTED]) _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
