Subj : Re: Ummmmmm
To   : stizzed
From : Accession
Date : Tue Jan 21 2025 06:25:18

Hey stizzed!

On Mon, Jan 20 2025 21:34:04 -0600, you wrote ..

>  At> The results of a misconfigured system...

> How so, please?

> My original post on this subject was regarding the presence of a .clo 
> file following an echomail export wherein it should have been deleted 
> by the system but wasn't. I dont think that you're saying that .clo 
> files are created due to a misconfiguration.  Perhaps you are saying 
> that the system failing to remove them is the result of a 
> misconfiguration?  If so can you please offer some thoughts as to what 
> this misconfiguration might be?  In my case this has happened once.  
> But of course, my ADHD would not allow me to just delete the file and 
> move on.  However, If I had misconfigured my system three years ago 
> when I set this network up I would expect to have seen this before but 
> perhaps not?  I understand what .clo files are and that they should be 
> removed by the system but thats pretty much the end of my knowledge. 
> However, Im certainly no expert on this which of course is the reason 
> I posed the question here.  Therefore, I would absolutely appreciate 
> you expanding on your assertion that its a misconfiguration at the 
> root of this problem.  If it is I'd very much wish to correct it.

If it only happened once in all that time, I wouldn't worry about it. Unless you saved the file for further investigation, there's really no need to try to look into it any more, as you don't have the proper information (the .clo file's first 8 letter/number combination is hex for the system it's supposed to be sent to).

This could have happened during a forced reboot, where a .clo file wasn't given a chance to be deleted the proper way. The "crash" attribute could have been accidentally set (using something like Golded) on something that wasn't configured for it in your tosser, etc. There's a few possibilities that won't be able to be checked unless you have the actual logs of that .clo file being created, or the file itself.

If you've manually deleted this file, no need to keep investigating it unless it happens again. If it does happen again, keep the file so you can check what node number it was destined for. Otherwise, it's really not that big a deal - especially if it doesn't happen again for another few years. :)

Regards,
Nick

.... He who laughs last, thinks slowest.
--- SBBSecho 3.23-Linux
 * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (46:1/700)

.