As far as I know that means it's finished, since amstatus looks for a
'work-in-progress' log instead of a completed log.
When I had a problem like this, it turned out that sometimes my sendmail
wasn't getting DNS, so the messages sat in a queue, and would eventually
have been bounced. Does procmail have a similar queue?
-----Original Message-----
From: Eric Wadsworth [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 30, 2000 5:11 PM
To: Bort, Paul; [EMAIL PROTECTED]
Subject: Re: Why no reports?
Yes, this was actually the first thing I did:
% amstatus DailySet1
no /usr/local/etc/amanda/DailySet1/log/amdump file at
/usr/local/sbin/amstatus
line 87.
I assume that this means it finished?
--- Eric
"Bort, Paul" wrote:
>
> I would suggest running amstatus <configname> to make sure it really did
> finish. I usually don't get a report when it's waiting for user input.
>
> -----Original Message-----
> From: Eric Wadsworth [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 30, 2000 4:43 PM
> To: [EMAIL PROTECTED]
> Subject: Why no reports?
>
> Been setting up Amanda, and she seems to be happy. Ran nightly (as spawned
> by
> cron) for the past two nights. For some reason, however, I didn't get an
> email
> report from last night's run. What could cause this? I looked at lots of
> different things, and it *looks* line it ran fine last night. This is the
> first
> time its failed to send a report, in the past I would always get 'em.
>
> Here's the line from amanda.conf:
>
> mailto "[EMAIL PROTECTED] [EMAIL PROTECTED]"
>
> I've been fiddling with procmail to handle the report that is sent to the
> operator account, but it appears that it didn't get one either.
===========================================================
Eric Wadsworth email: [EMAIL PROTECTED]
Conceptual Systems and Software http://www.consys.com
===========================================================
