|
Re: smbtar
2003-08-12 02:04:08
The problem I'm having is that I can't
get smbclient to work properly when it's wrapped in a script.
What I have done is rename smbclient
to smbclient.am and create a script (smbclient) that calls smbclient.am
with the same command line parameters the script itself gets.
(I had to rename smbclient because no
matter what I tell configure to use in --with-smbclient Amanda insists
on using /usr/bin/smbclient )
amcheck seems to work, but amdump doesn't.
I would like a working example of such
a script (if possible)
TIA
Bert
|
| Jon LaBadie <jon AT jgcomp DOT com>
Sent by: owner-amanda-users AT amanda DOT org
11/08/2003 18:37
Please respond to amanda-users
|
To:
amanda-users AT amanda DOT org
cc:
Subject:
Re: smbtar |
On Mon, Aug 11, 2003 at 05:22:26PM +0200, Bert_De_Ridder AT peopleware DOT be
wrote:
> Anybody who remembers how this script was set up ?
>
>
> Jon LaBadie <jon AT jgcomp DOT com>
> 11/08/2003 16:23
>
> To: Bert_De_Ridder AT peopleware DOT be
> cc:
> Subject: Re:
smbtar
>
>
> On Mon, Aug 11, 2003 at 03:47:30PM +0200, Bert_De_Ridder AT peopleware DOT be
> wrote:
> > Any chance I can create a wrapper script around smbclient ?
> > (like I do with gnutar )
> >
>
> At least on list member, maybe 18 months ago, did that to implement
> a multi-file exclude feature. Amanda, as distributed, only one
file
> can be specified as being excluded when using samba.
>
If you mean the logic of multiple excludes, they were passed as a file
containing the list (as per exclude list or exclude append) and the
script converted the list into command line args. Something like:
ExcludeListFile=$???
# some cmd line arg
ExcludeList=
for Next in $ExcludeListFile
do
ExcludeList="$ExcludeList $Next"
done
Then $ExcludeList was used on the real smbclient command line after
the "X" option, I think as the last args on the cmd line.
--
Jon H. LaBadie
jon AT jgcomp DOT com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
|
|
