Dave Kleikamp wrote:

> 
> On Thu, 2008-02-28 at 12:29 +0100, Per Jessen wrote:
>> Per Jessen wrote:
>> 
>> > Dave, you suggested stracing the make, but that'll be difficult -
>> > the make is run about once every 1-2 seconds, and without being to
>> > reproduce the problem on demand, that's a lot of stracing :-)
>> > What else could I strace?  Would it help tracing the 'mv'?
> 
> Looking at it again, I still don't have any bright ideas on what is
> happening.  Would it be possible to share the actual makefile?  The
> little example in the initial report doesn't seem right.

No probs, here it is:

http://jessen.ch/files/Makefile.quarantineupdate-perdomain  

New files are put into "quarantined/new/" - the Makefile will pick these
up, and as the first thing move them into "quarantined/cur/".  The rest
of the processing happens on files in "quarantined/cur/".  It just
looks like sometimes the file is copied to /cur/, but not deleted
from /new/.

> test -f source && false
> 
> "&& false" ensures that it will fail no matter what.

Yeah, that wasn't the entire line.  Sorry - with the strace, it really
looks like this:

quarantined/cur/%:  quarantined/new/%
        strace -o quarantined/$*.strace mv $< $@
        test -f $< && mail MYEMAILADDR <quarantined/$*.strace || rm -f
quarantined/$*.strace

>> I've put an strace on the 'mv' - the trace output is emailed to me if
>> the mv doesn't actually move the file.
> 
> I trust you'll let me know if you find out anything more.

Yep, willdo.  


/Per Jessen, Zürich


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion

Reply via email to