RE: PAR + tmpwatch = mess
[email protected] (Markus Jansen)
| Newsgroups | perl.par |
|---|---|
| Message-ID | <[email protected]> |
Hi,
regarding the intended behaviour, that is if the canary file is the youngest file after unpacking, I don’t have any objections at all.
My point was simply that the unpacking modification might break some code.
Cheers,
Markus
From: [email protected] [mailto:[email protected]] On Behalf Of Roderich Schupp
Sent: Monday, June 22, 2015 2:15 PM
To: Markus Jansen
Cc: Shawn Laffan; [email protected]
Subject: Re: PAR + tmpwatch = mess
On Fri, Jun 19, 2015 at 1:38 PM, Markus Jansen <[email protected]<mailto:[email protected]>> wrote:
I would not recommend the canary mode as a default, unless we have found that it is reasonable to do so.
Why not? If a user is still invoking the packed executable once in a while, the
canary avoids the situation that he has an incomplete cache area.
If they don't invoke the packed executable anymore, the cache area will be
cleaned up eventually by tmpwatch or whatever, no harm done.
Sorry to pick on this: pp has too many options already.
Cheers, Roderich