On 16 Apr 01 at 23:01, owner-arachne-digest@arachne wrote:
>Date: Mon, 16 Apr 2001 14:27:04 -0500
>From: "L.D. Best" <[EMAIL PROTECTED]>
>Subject: Bugs?? #3 -- File being rewritten for no reason
>
>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?
This file is just a flag to indicates that Arachne is running. You
will have problems if you start Arachne twice at the same time from
the same directory (e.g. in task switching environment or by
shelling out). This is why arachne.bat controls whether there is a
lock file in the directory. If there is not then it creates it and
starts the program. If the file is already existing, you will get a
warning message.
>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.
The only way to control this is replacing arachne.cfg with your
own configuration backups (.ACF files) before starting the program.
Arachne does not ask for anybody's advice when she has to write a
configuration files. She will just do it, when she likes to do so.
She likes to do so very much and very often.
Regards
Christof Lange
