At 23:34 2005-03-19 +0100, Michelle Konzack wrote:
> > which check for
> >the lockfile and if there is none, download the $SOURCE ?
>
> Why would the fetchmail need to be within a lockfile wrapper? Seems that
> would still manage to hold up your mail processing.
If there is an incoming message, it will be better to generate a
lockfile, because of the writing the body to a file like
Er, that's fine to lock a RECIPE (and if you're outputting to a file, you
should), but why lockfile the whole fetchmail invocation (which seems to be
what you said in your original post)?
If procmail write the body of the message to the file above and
my script try to access it, maybe the script run into trouble...
Not the body of the message - your procmail recipe can extract the package
name identified in the message and create a zero-length file of that name,
thereby adding it to the "queue".
> Using a cron-invoked script allows for more simplistic error recovery than
> using at - if the script simply doesn't delete the stub file from the
> request directory unless it succeeds, then the next invocation can attempt
> to retrieve it again, without any special retry coding on your part. With
OK, 'dpkg-buildpackage' return an "exit status" which I can ise to
change the fileneme from
[snip]
Ok.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail