Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: tandum on June 15, 2006, 04:09:49 PM

Title: TAR behaviour change in RC3
Post by: tandum on June 15, 2006, 04:09:49 PM

I have a script running on several SME boxes that uses tar. After upgrading a couple of boxes to RC3 tar is now verbose when using the --after-date option. The non upgraded boxes are still ok.

This is the redirect statement from the script :-

exec 3>&1                        
exec 1>$LOGFILE              
exec 2>&1                        
if [ $QUIET -eq 0 ]
  then tail -f $LOGFILE >&3 &
fi

and here is the problem tar statement :-

      tar --create $VERBOSECOMMAND \
        --file $OUTFILE \
        --after-date "$LAST" \
        --label "Level-$LEVEL Backup from $LAST to $NOW" \
        $BACKUPFILES

The log file is full of ... "<path to file> no change not dumped" entries.

Only tar commands using the --after-date option do this but they are the only ones that would output that message.

Any clues ?

Title: TAR behaviour change in RC3
Post by: tandum on June 15, 2006, 04:13:43 PM

I just saw this one and will try commenting it out.  It captures errors. But still it's different in RC3.
exec 2>&1

Title: TAR behaviour change in RC3
Post by: tandum on June 17, 2006, 11:59:15 AM

Yes all those messages are coming out std error when they never did before.
RC3 uses tar-1.14-10 while RC2 used tar-1.14-9 so the newer build is a lot more verbose than before. I've dropped back to the earlier version for sanity sake.

Title: TAR behaviour change in RC3
Post by: dtech on June 18, 2006, 05:40:07 AM

There doesn't seem to be a switch to turn verbosity down. I'm getting 3MB emails every morning with the results of a cron backup script. Can this be considered a bug?

Title: TAR behaviour change in RC3
Post by: dsemuk on June 18, 2006, 10:55:56 AM

Quote from: "dtech"

There doesn't seem to be a switch to turn verbosity down. I'm getting 3MB emails every morning with the results of a cron backup script. Can this be considered a bug?

Please put it in the bug tracker, I'm sure the developers would rather it be in the bug tracker then at least they can decide what has to be done about it.

Dave

Title: TAR behaviour change in RC3
Post by: TrevorB on June 19, 2006, 04:45:47 AM

Quote from: "tandum"

RC3 uses tar-1.14-10 while RC2 used tar-1.14-9 so the newer build is a lot more verbose than before. I've dropped back to the earlier version for sanity sake.

tar-1.14-10 is a security update from redhat (fixes a security vulnerabilty).

Not sure if you want to revert.....

It is EXTREMELY unlikely that the developers will want to regress a security patch.

Please remember that smeserver is based on Centos 4 (which is based on RedHat ES4), and that tar is part of the base Centos install, so you need to look for information/fixes at RedHat.

Title: TAR behaviour change in RC3
Post by: dtech on June 21, 2006, 03:55:11 AM

Now in bugzilla here: http://bugs.contribs.org/show_bug.cgi?id=1621

Title: TAR behaviour change in RC3
Post by: tandum on June 21, 2006, 03:01:22 PM

Quote from: "TrevorB"

tar-1.14-10 is a security update from redhat (fixes a security vulnerabilty).

I see tar-1.14-10 as a bug fix : http://rhn.redhat.com/errata/RHBA-2006-0336.html.
tar-1.14-9 is listed as a security update : http://rhn.redhat.com/errata/RHSA-2006-0232.html
There are a few rpm's about for 1.15-x so that will prolly show up in the updates eventually.