-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gene Heskett schrieb:
> On Friday 26 March 2010, Michael Mueskens wrote:
>> how exactly did you do that? Did you change something in the
>> amanda-source? Is this error output not from the client, so you have to
>> patch something in the amanda-client-code?
>> I'm having that problem since upgrading my _servers_ to 2.6.1p2 too, so
>> I'd be quiet interested in any way to suppress that non-error? :)
> 
> In bash, you can assign that error and process accordingly.  Here is a 
> snippet of that part of my wrapper script, with the language sanitized 
> for the list:
> 
>        ${AM_SBIN_DIR}/amdump $CONFIGNAME $HOST $DLE >> $LOG
>         SCS=$?
>         echo ${AM_SBIN_DIR}"/amdump "$CONFIGNAME $HOST $DLE" returned "$SCS 
> >>$LOG
>         if [[ $SCS -ne "0" ]] ; then
> # according to the info page, any error is "probably a 2" return.  Dumb, 
> effing dumb.  Real effing dumb even.
> # so apparently a file that got changed in the users maildir is an error.  
> Its gonna happen, just ignore it.
>                 if [[ $SCS -gt "2" ]] ; then
>                         echo "amdump THINKS it or tar failed for some reason, 
> see the $LOG file." |tee -a $LOG
>                 fi
> 
> The $? transfers the return value to the SCS variable. $SCS is then checked 
> to see if its a real error.
> 

hello,

okay, I see, you don't use the amanda-commands directly. Do I get it right, that
in the above example you have a wrapper to start dumps? How do you treat
amreports? Do you wrap them too?
Actually I don't want to do something like that, I'm starting amdump via cronjob
(okay, matter of fact I do use a wrapper-script to change the data-link to the
correct virtual-tape, amcheck -c and then start amdump), but I'm letting amanda
do what it's supposed to do: Backup my clients and send a report about it.
I was hoping of a way to let amanda recognize _directly_ that "file changed as
we read it" is no error :)

Michael

- --
Michael Müskens

Rule #18: It's better to seek forgiveness than ask permission.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkus19UACgkQWjIj1fb8pFsl6wCdGDvMNl3ueamhaELtLY9e934M
olwAn3a9RTKjg28xBpgyrA71WnF2sjKL
=fu+l
-----END PGP SIGNATURE-----

Reply via email to