Subj : Re: 'conflicted' files
To   : g00r00
From : Black Panther
Date : Sat Nov 27 2021 03:18 pm

On 27 Nov 2021, 02:38p, g00r00 said the following...
 
 g0> There is nothing in Mystic that does this that I can think of anyway. 
 g0> Are you using a networked file share of some sort that could be doing
 g0> this while there are conflicts in files?  Or a VMware with shared
 g0> directories or anything like that?

Nope. This is on my test system, which everything is run locally. I do have network file shares, but nothing with this drive.

I do think I might have found, at least part, of the problem. I was logged into Mystic, using ./mystic -l, and also logged into another node with the same user name. (I had one terminal at 80x25, and one at 132x37) After noticing the issue with the 'conflicted' files, I did see in the error.log that Mystic couldn't write to the chat1.dat file. It looked like I still had active logins to Mystic, but both the chat1.dat and chat2.dat files were missing.

This is running a slightly older pre-alpha version of Mystic, (2021/08/29) so maybe I really need to update... ;) I'm wondering if it might be related to the issue that someone else had with being dropped to a command prompt when running locally...


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

.... My software never has bugs. It just develops random features...

--- Mystic BBS v1.12 A47 2021/09/07 (Linux/64)
 * Origin: Castle Rock BBS - bbs.castlerockbbs.com (1:317/3)

.