[Samba] Updated from 2.2.8a to 3.0b3 gives smbtar newer failure

Mark Cooke mpc at star.sr.bham.ac.uk
Thu Jul 31 11:10:27 GMT 2003


Workaround:

1. I pulled smbtar and smbclient from 2.2.x
2. Renamed then to smbtar.2x and smbclient.2x
3. Edited smbtar.2x references to smbclient to be smbclient.2x
4. Put the /usr/share/samba/codepages from 2.2.x back in place
5. Changed the backup scripts to call smbtar.2x

All is working again.

Bit more data about the fault in 3.0b3 smbclient:

The option parsing in smbclient for the tar options is strangely wrong.

tar files were being created, but with the name of the share being
accessed, not the requested tar file or stdout.

I assume a similar problem is affecting the newer-file option parsing
too, but lack of a valid file to date from caused an abort.

Cheers,

Mark

On Thu, 2003-07-31 at 03:43, Mark Cooke wrote:
> Hi all,
> 
> Situation:
> 
> We use smbtar for backups, incrementals done using -N <last date file>,
> and this has worked well with samba 2.2.x
> 
> After upgrading to 3.0b3, using the -N (newer) option to smbtar causes a
> bad interaction with smbclient.
> 
> Eg,:
> 
> # smbtar -s PC -x Share -u User -p Pwd -d / -t - -N last-backup -v
> 
> gives (if you print out the eval at the end of smbtar script):
> 
> eval /usr/bin/smbclient '\\PC\Share' 'Pwd' -U 'User' -E -N -d 2 -D '/'
> -c 'tarmode full' -TcN last-backup - ${1+"$@"}
> 
> giving:
> 
> [backup at pc1 CADPC6]$ cat Team.tar.log
> Error setting newer-than time
> Usage: [-?|--help] [--usage] [-R|--name-resolve NAME-RESOLVE-ORDER]
>         [-M|--message HOST] [-I|--ip-address IP] [-E|--stderr]
> [-L|--list HOST]
>         [-t|--terminal CODE] [-m|--max-protocol LEVEL] [-T|--tar
> <c|x>IXFqgbNan]
>         [-D|--directory DIR] [-c|--command STRING] [-b|--send-buffer
> BYTES]
>         [-p|--port PORT] [-d|--debuglevel DEBUGLEVEL]
>         [-s|--configfile CONFIGFILE] [-l|--log-basename LOGFILEBASE]
>         [-V|--version] [-O|--socket-options SOCKETOPTIONS]
>         [-n|--netbiosname NETBIOSNAME] [-W|--workgroup WORKGROUP]
>         [-i|--scope SCOPE] [-U|--user USERNAME] [-N|--no-pass]
> [-k|--kerberos]
>         [-A|--authentication-file FILE] service <password>
> 
> 
> Removing the -TcN <file> and replacing it with -Tc fixed this gotcha.
> 
> Cheers,
> 
> Mark
> 
> -- 
> Mark Cooke <mpc at star.sr.bham.ac.uk>
-- 
Mark Cooke <mpc at star.sr.bham.ac.uk>




More information about the samba mailing list