On Tue, 25 Feb 2003, Stas Bekman wrote:
> > -rw-rw-r-- 1 perlwww perl 1441405 Feb 24 06:43 index.swish-e.prop
> > -rw-rw-r-- 1 perlwww perl 4777362 Feb 24 06:43 index.swish-e
>
> The cron runs several times a day, so may be it was successful on the next
> build.
The error message has this as a date:
Date: 24 Feb 2003 14:43:26 -0000
so it seems like the same run.
>
> > When swish indexes it writes to .temp files, then at the very end renames
> > the files removing the .temp suffix.
> >
> >
> > void DB_Reopen_PropertiesForRead_Native(void *db)
> > {
> > struct Handle_DBNative *DB = (struct Handle_DBNative *) db;
> > int no_rename = 0;
> > char *s = estrdup(DB->cur_prop_file);
> >
> > /* Close property file */
> > DB_Close_File_Native(&DB->prop, &DB->cur_prop_file, &no_rename);
> >
> >
> > if (!(DB->prop = openIndexFILEForRead(s)))
> > progerrno("Couldn't open the property file \"%s\": ", s);
> >
> > DB->cur_prop_file = s;
> > }
> >
> > progerrno() calls exit.
>
> so, why the error?
The error said
err: Couldn't open the property file "index.swish-e.prop.temp": No such file
or directory
so it doesn't really make sense. Get an abort message at 14:43, but
there's index files created at 14:43 anyway. Happen only once in a while.
Any chance that there's two cron entries? Seems very unlikely, but only
thing I can think of.
--
Bill Moseley [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
