Re: Problems with amsamba on Debian Jessie since upgrade

2016-04-20 Thread Stefan G. Weichinger
Am 20.04.2016 um 15:30 schrieb Jean-Louis Martineau: > It's hard to fix documentation when user don't tell how to improve it. > Can you tell us the additional stuff? You are right, sorry. I just wanted to wait for an example, maybe I misunderstood something etc My definitions so far, note commen

AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]

2016-04-20 Thread Tobias Köck
Hi Jean-Louis, my smb.conf already has the entry syslog = 0 so I don't know where that came from. Still the amsamba application exits with 1 localhost: Application 'amsamba': exited with status 1 Shouldn't it be something else? It still is 'just' a warning? Anyway, thanks for your help. I'll

AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]

2016-04-20 Thread Tobias Köck
Hi Jean-Louis, I have applied your patch. Unfortunatelly that didn't work either. I have attached one log and the amcheck -c someconfig output. ---amcheck-- backup@chronos:~$ amcheck -c somec

AW: AW: sendbackup: critical (fatal): error [no backup size line]

2016-04-20 Thread Tobias Köck
For some reason the MUA didn't transfer the newline characters for the entries but the entries are in separate lines. -Ursprüngliche Nachricht- Von: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] Im Auftrag von Tobias Köck Gesendet: Mittwoch, 20. April 2016 11:27 An

AW: AW: sendbackup: critical (fatal): error [no backup size line]

2016-04-20 Thread Tobias Köck
Hi Jean-Louis, sure. I have adjusted the password and some URLS/IPs. Relevant and activated for amsama are the monster.someurl.de entries. # nas shares //192.168.210.254/tempstorage backup%somepassword //192.168.210.254/a2g_it backup%somepassword //192.168.210.254/a2g_intern

Re: WORM media

2016-04-20 Thread Stefan G. Weichinger
Am 2016-04-19 um 01:06 schrieb Debra S Baddorf: > I forgot to reply — I’ve just started using specific DLEs inside of > disklist (I had been creating differently named dumptypes inside of > amanda.conf) so I’ll have to look at that too. But I also use named > dumptypes inside of other named d