alpha: 4 jobs and crawling?

[Peter Knowles]

What the code actually does is the following. All temporary files are
unlink(2)ed immediately after they are created. This means that they are
not tied to a directory, with the consequence that you will not see them
with ls, nor will their space be counted with du. However, the files are
still there, and you will certainly see their presence in the output
from df. The reason for doing things this way is that the files
automatically disappear when they are closed or when the process owning
them dies; thus even when Molpro terminates abnormally, your scratch
disk is not left full of useless data.

Under circumstances (for example, if your job scheduler checkpoints), it
may be desirable to keep the files visible. This can be enabled by
inserting
-DKEEPTEMP
into the CDEF stanza in CONFIG, then doing rm -f src/util/iow_direct.o;
make

Peter

--
Prof. Peter J. Knowles
Email P.J.Knowles at bham.ac.uk  Phone +44-121-414-7472  Fax
+44-121-414-7471
School of Chemical Sciences, University of Birmingham, Birmingham, B15
2TT, UK
WWW http://www.tc.bham.ac.uk/~peterk/


> -----Original Message-----
> From: owner-molpro-user at molpro.bham.ac.uk [mailto:owner-molpro-
> user at molpro.bham.ac.uk] On Behalf Of Pawel Dziekonski
> Sent: 17 June 2003 12:48
> To: Thomas Weber
> Cc: molpro-user at molpro.net
> Subject: Re: alpha: 4 jobs and crawling?
> 
> On wto, 03 cze 2003 at 03:15:55  +0200, Thomas Weber wrote:
> > Am Dienstag, 3. Juni 2003 14:49 schrieb Pawel Dziekonski:
> >
> > > it is obvious that M. jobs "interfere" with each other in some
way.
> > > they are definitely not swapping!  my 1st suspect-ion was that i/o
is
> so
> > > intensive however I can't find ANY temporary files created by
those
> > > jobs. where are they???
> >
> > Molpro files are invisible. They are marked deleted.
> 
> if they are marked deleted, does du/df count them ?
> 
> --
> Pawel Dziekonski <pawel.dziekonski|@|pwr.wroc.pl>, KDM WCSS
avatar:0:0:
> Wroclaw Networking & Supercomputing Center, HPC Department
> -> See message headers for privacy policy info.