Meik Hellmund wrote:
Hi,This should work fine...I did it on the off chance I may decide to write a wrapper script to do something simliar but aven't seen the need in my environment yet so I just copied the tar binary where I told it to look for now.
I would like to use the fssnap facility for snapshots on Solaris and write a
wrapper script. It seems to me that the paths to tar and dump are hardcoded
to amanda at compile time. Is it possible to avoid recompilation of the amanda client by giving another path to tar/dump at runtime?
If not, is it somehow possible to check whether the script was called byYou can either read through the code or just let amanda runs once and look at her debug files as it gives pretty much everything it did there (this is one thing I really like about Amanda since I can see what she's trying to do at every step)
amanda? Perhaps amanda sets some environment variabel so that I can write
#!/bin/sh
if [ ! $CALLED_BY_AMANDA ] ; then ufsdump.orig $*
exit fi
.... amanda stuff ...
The script should check if this is the estimate run or the "real" run and
for the real run the device/directory argument has to be changed to
point to the new snapshot device. So, is it somewhere documented how the argument list produced by amanda looks like?
=G=
