L.D. Best wrote:
>
> I discovered something very interesting when I was hunting for the
> elusive snark on my HDD ...
>
> lock This was written when I started Arachne at 12:17 today. WHY?
I find this file annoying also, but it is there to prevent you from trying
to run two Arachnes. Like, you shell out, and forget that you are shelled
and instead type Arachne (or Spider or whatever).
The annoyance comes from running into it when I do exactly what it is
designed to prevent. <G> Or sometimes you crash - therefore exiting
Arachne abnormally - and leaving the lock file intact.
> arachne.cfg This was rewritten at 12:33 today, although I'd made no
> changes to it and had done nothing with Arachne except go
> to the Inbox on boot-up and hit "R" to reload a correct
> version of the inbox index, and written one message which
> asked the question about that incorrect index.
Arachne re-writes Arachne.cfg an awful lot more often than you might
expect - giving plenty of opportunities to corrupt it.
> cookies.lst This was rewritten today at 12:30, although all I'd done
> was start Arachne.
>
> It was RErewritten again at 13:05 when I quit [ALT-X]
>
> Every time a file is rewritten for no purpose whatsoever, it slows down
> processing time and also makes errors more likely to occur.
Yup.
> Why the cookie list should be written on EXIT is beyond my
> understanding, unless someone somehow linked rewriting cookie.lst to
> whenever history.lst is rewritten -- and that makes no sense whatsoever.
Yup.
- Clarence Verge
--
- Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
- The internet is infected - Windows is a VIRUS !!
--
