Subj : Re: The var/ticqueue directory?
To   : Vince Coen
From : Rj Clay
Date : Sun Dec 03 2017 10:57:46

Vince Coen wrote to Rj Clay: 
VC> Saturday December 02 2017 04:58, you wrote to me:

VC> 
VC>  >    So inactive .tic files would be ones that have already been sent,
VC>  > and at least in more recent versions get automatically cleaed up?
VC>  > (That was one of concerns as lots of tiny files can really jump up
VC>  > inode usage...)
VC> 
VC> The nightly script clears these and files/mail that has been sent out from 
VC> the outbound directories etc but after the files / mail have been sent

    So old files there are a pretty good sign of FTN sessions not
happening preperly or not being connected to the node that the files are for? 
Easier to see in the ticqueue, since it's a single directory, but relatively
easy still to compare against the 'mbout sta' output.


VC> If you are going to use mbse over a previous BBS then you may well also 
VC> want to adopt all of the various bbs file areas into mbse using mbfile.

   There's a separate issue regarding that as all of the public files areas
are/were kept in separate, from the Mbse BBS install,  directories, and that 
it
 turns out I didn't have a backup of.

   So there are a lot of files in the BBS files database that are not actully
present.  Presumably I can take are of this by putting the files were it 
thinks
 they are but I need to decide which ones to to that for...



Jame 

    Greetings, Rj Clay
    email: admftn@ftn.rocasa.net

--- MBSE BBS v1.0.6.8 (GNU/Linux-i386)
 * Origin: ftn.rocasa.net (1:120/544)

.