Benjamin Gonay <gonay(_at_)goliath(_dot_)is(_dot_)belgacom(_dot_)be> writes:
But when i look in the logfile of procmail, i still see errors.
These errors seems not to be 'fatal' because my script is well executed.
Could someone can explain it to me ?
Here's the error :
procmail: Couldn't determine implicit lockfile from "meteo_satt"
From BITFTP1(_at_)PUCC(_dot_)PRINCETON(_dot_)EDU Wed Feb 5 06:40:02 1997
Subject: satt0.jpg, Part 001 of 001 (uuencoded)
Folder: meteo_satt 142500
Well, let's take a look at the DIAGNOSTICS section of the procmail(1)
manpage:
Couldn't determine implicit lockfile from "x"
There were no `>>' redirectors to be
found, using simply `$LOCKEXT' as lo-
callockfile.
I.e., you have a 'pipe' action on a recipe with an implicit
locallockfile, but procmail was unable to figure out what file to
lock. You should either:
a) explicitly name the lockfile on the ":0" line; or
b) if it's okay for two copies of "meteo_satt" to be running, remove the
second colon.
And the 'meteo_satt' is :
uudecode
chmod 644 satt*
mv /doc/www/gif/satt0.jpg /doc/www/gif/satt0_J-1.jpg
mv satt* /doc/www/gif
Well, this looks like something which shouldn't have two copies running
simultaneously, so you should go ahead and put an explicit lockfile name
in.
BTW: do you do any checking to make sure you don't decode a file
"../../.rhosts" (or whatever it would take to overwrite your .rhosts
file)? uudecoding arbitrary data is a Bad Idea.
Nothing complicated... ;-)
What's better: pipe to a script or include script's command in the
procmailrc...?
If the script is used in more than one place, or *might* be used in more
than on place, then I'd leave it a script.
Philip Guenther