Hi Folks,
I've put together a script for sorting my backup files into sub folders to be run from a cron job. Each file is named username.tar.gz and the file /etc/trueuserowners contains all users and their owner in the format "user: owner".
The script works fine identifying users and their owners and is as follows:

Code:

#!/bin/bash
_w="/path/to/backups"
_wb="$_w/*.tar.gz"

if [ -d "$_w" ]; then
        for f in $_wb
        do
                _f=$(basename $f)
                _user=${_f%%.*}
                _o=`grep "^$_user:" /etc/trueuserowners`
                _owner=${_o#* }
                if [ ! -d "$_w/$_owner" ]; then
                        `mkdir $_w/$_owner/`
                fi
                `mv $f $_w/$_owner/`
        done
fi

Say I have the following:

/path/to/backups/userabackup.tar.gz
usera is owned by resellera.

The first time the script runs, the script will create the following directory and move userabackup.tar.gz into it:

/path/to/backups/resellera

The script has an if in it to ensure that /path/to.backups/resellera is only created if it does not already exist as you can see. My problem is that the mv command appears to be backing up the directory and creating a new one instead of moving the file into the existing directory and replacing the file if it is already there.

For example:

The second time the script runs, /path/to/backups/resellera will be renamed to /path/to/backups/resellera.1 and a new /path/to/backups/resellera is created.
The third time, /path/to.backups/resellera.1 is renamed /path/to.backups/resellera.2, /path/to.backups/resellera to /path/to.backups/resellera.1 and a new directory created.

I shouldn't need to have the script remove the directory first and the mv command does not create backup directories like this when run from the console. The VERSION_CONTROL environment is not set.
Is there something specific that makes mv act like this when run from a cron job? Do I have to tell it to over-write instead of create these backups?