Hello There,

In testing the importing of a "Filebone.na"file to create file areas.
I edited the existing mutil.ini file and saved the file as "fsx-file-na.ini". The actual uppercase FSX_FILE.NA file exists in the mystic directory and
is specified in the [Import_FILEBONE.NA] stanza as indicated below.

I then executed the commandline "./mutil fsx-file-na.ini. Below are the portion of the fsx-file-na.ini being used and also the MUTIL log entry.
The log indicates that 0 file areas were created. That was verified by
looking in Mystic config. I may be mistaken but the log seems to indicate
that a FILEBONE.NA was being used or at least expected to be seen as no mention of a FSX_FILE.NA file was mentioned. Even though the specified filename to use was FSX_FILE.NA. No FILEBONE.NA file exists in the Mystic directory. The log level in the .ini file is set to 3 as indicated in the
log file entry.

[General]

; list of functions to perform on startup

Import_FILEBONE.NA = true

[Import_FILEBONE.NA]

; filename of filebone.na

filename = FSX_FILE.NA

; root directory to create file paths under. when a new filebone echo
; is found, mUtil will create a file using "root_dir" + areatag. So
; for example if root is "c:\mystic\filebase\" and the areatag is
; MYSTICBBS it will create "c:\mystic\filebase\MYSTICBBS". This root
; directory MUST exist.

root_dir = /home/bbs/mystic/files/fsxnet/

; convert tags to lower case for filebase base filename/dir 1=yes

lowercase_filename = 1

; Default values when creating a new file base

dispfile =
template = ansiflst
acs_list = s50g2
acs_ftp = s50g2
acs_download = s50g2
acs_upload = s255g2
acs_hatch = s255g2
acs_sysop = s255g2

; true/false type values 0=false 1=true (newscan 2=forced)

free_files = 0
show_uploader = 1
new_scan = 1

MUTIL log entry:

----------------- MUTIL v1.12 A36 2017/11/26 Tue, Nov 28 2017 (loglevel 3)
+ Nov 28 16:30:47 Startup using fsx-file-na.ini
- Nov 28 16:30:47 EXEC Import_FILEBONE.NA
+ Nov 28 16:30:47 Process: Import FILEBONE.NA
+ Nov 28 16:30:47 Results: Created 0 base(s) in 0.00s
+ Nov 28 16:30:47 Shutdown Normal (0)

I tried including the full path to the FSX_FILE.NA file in the .ini file
entry for filename = FSX_FILE.NA but got the same 0 file areas created.

I then tried renaming the FSX_FILE.NA file to FILEBONE.NA file and edited the fsx-file-na.ini file to reflect the filename change but got the same 0 file areas created.

I am certainly not above missing the simple things. It seems the little
things can often be sneaky and hide in plain site. :-)

So, the resulting question is did I miss something?



Jeff

--- Mystic BBS v1.12 A36 2017/11/26 (Linux/64)
* Origin: New Mystic BBS (21:1/128.3)

What's the na file look like

On 11:30 28/11 , Jeffs wrote:

Hello There,

In testing the importing of a "Filebone.na"file to create file areas.
I edited the existing mutil.ini file and saved the file as "fsx-file-na.ini". >The actual uppercase FSX_FILE.NA file exists in the mystic directory and
is specified in the [Import_FILEBONE.NA] stanza as indicated below.

I then executed the commandline "./mutil fsx-file-na.ini. Below are the >portion of the fsx-file-na.ini being used and also the MUTIL log entry.
The log indicates that 0 file areas were created. That was verified by >looking in Mystic config. I may be mistaken but the log seems to indicate >that a FILEBONE.NA was being used or at least expected to be seen as no >mention of a FSX_FILE.NA file was mentioned. Even though the specified >filename to use was FSX_FILE.NA. No FILEBONE.NA file exists in the Mystic >directory. The log level in the .ini file is set to 3 as indicated in the >log file entry.

[General]

; list of functions to perform on startup

Import_FILEBONE.NA = true

[Import_FILEBONE.NA]

; filename of filebone.na

filename = FSX_FILE.NA

; root directory to create file paths under. when a new filebone echo
; is found, mUtil will create a file using "root_dir" + areatag. So
; for example if root is "c:\mystic\filebase\" and the areatag is
; MYSTICBBS it will create "c:\mystic\filebase\MYSTICBBS". This root
; directory MUST exist.

root_dir = /home/bbs/mystic/files/fsxnet/

; convert tags to lower case for filebase base filename/dir 1=yes

lowercase_filename = 1

; Default values when creating a new file base

dispfile =
template = ansiflst
acs_list = s50g2
acs_ftp = s50g2
acs_download = s50g2
acs_upload = s255g2
acs_hatch = s255g2
acs_sysop = s255g2

; true/false type values 0=false 1=true (newscan 2=forced)

free_files = 0
show_uploader = 1
new_scan = 1

MUTIL log entry:

----------------- MUTIL v1.12 A36 2017/11/26 Tue, Nov 28 2017 (loglevel 3)
+ Nov 28 16:30:47 Startup using fsx-file-na.ini
- Nov 28 16:30:47 EXEC Import_FILEBONE.NA
+ Nov 28 16:30:47 Process: Import FILEBONE.NA
+ Nov 28 16:30:47 Results: Created 0 base(s) in 0.00s
+ Nov 28 16:30:47 Shutdown Normal (0)

I tried including the full path to the FSX_FILE.NA file in the .ini file >entry for filename = FSX_FILE.NA but got the same 0 file areas created.

I then tried renaming the FSX_FILE.NA file to FILEBONE.NA file and edited the >fsx-file-na.ini file to reflect the filename change but got the same 0 file >areas created.

I am certainly not above missing the simple things. It seems the little >things can often be sneaky and hide in plain site. :-)

So, the resulting question is did I miss something?

Jeff

--- Mystic BBS v1.12 A36 2017/11/26 (Linux/64)
* Origin: New Mystic BBS (21:1/128.3)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A36 2017/11/28 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

- Nov 28 16:30:47 EXEC Import_FILEBONE.NA
+ Nov 28 16:30:47 Process: Import FILEBONE.NA
+ Nov 28 16:30:47 Results: Created 0 base(s) in 0.00s
+ Nov 28 16:30:47 Shutdown Normal (0)

The import prints errors in all cases within the log except when the .NA file format is wrong or Mystic doesn't like its contents might be a better way to describe it :) Mystic assumes they're comments and doesn't print an error.

It doesn't look like you're doing anything wrong. I think what we need to look at is the format of the .NA file and see if the format is different from what Mystic expects, or if Mystic just can't parse it.

Since its not even logging anything that implies that either the first word
in the file is not "AREA" or the 4th word in the file does not contain a !

--- Mystic BBS v1.12 A36 2017/11/27 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/28/17, g00r00 pondered and said...

It doesn't look like you're doing anything wrong. I think what we need
to look at is the format of the .NA file and see if the format is different from what Mystic expects, or if Mystic just can't parse it.

Since its not even logging anything that implies that either the first word in the file is not "AREA" or the 4th word in the file does not contain a !

I should test this also seeing I created it :) It was based on an othernet
file so I expected it to work.. Humm..

You can find it in any fsxNet infopack..if somethings amiss, I'm happy to change it.

Best, Paul

--- Mystic BBS v1.12 A36 2017/11/26 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 11/29/17, Avon said the following...

Since its not even logging anything that implies that either the firs word in the file is not "AREA" or the 4th word in the file does not contain a !

I should test this also seeing I created it :) It was based on an
othernet file so I expected it to work.. Humm..

You can find it in any fsxNet infopack..if somethings amiss, I'm happy to change it.

I just compared it to other filebone.na files, and there is a slight issue.

It should be in the format of:
Area FSX_NODE 0 ! Weekly Nodelists (fsxNet, etc.)
etc...

I think all you need to add is the exclamation point (!) between the 0 and
the description of the file echo. It just indicates that these areas have filebone distribution.

snip<=-

%============================================================================= % || Key to Listings || %============================================================================
%
%
% The following format is used to describe each of the File Distribution Areas %
% Kywd FileTag Level Flags Description
% ---- -------- ---- ----- -------------------------------------------- % Area XYZ_GIF 0 ! XYZ: GIF files for the XYZ program
% ^ ^ ^ ^ ^ % COL:1 1 2 2 7 % 6 2 9 8 %
%
% "Area" - Used by ALLFIX and similar programs to denote the
% beginning of an file area definition.
%
% FileTag - Name of area that files will be sent under. Similar to an % echomail areatag, but limited to 8 characters or less.
%
% Level - Security level (0-4096) used to protect this area
%
% Flags - Access flags (see below) to control who's allowed to feed, % and what type of echo it is.
%
% Desc - Description of the area's contents.
%
% There are five types of access flags:
%
% "!" - Filebone distribution. Areas marked with this flag are carried by % the Filebone and can found at any Filebone Hub site (see below).
%
% "." - Open distribution. While unrestricted in nature, these areas are
% *NOT* distributed by the Filebone. Although many Filebone Hubs do % in fact carry them, you may be forced to find your own feed.
%
% "*" - Hatching is allowed by *any* node attached to the area. This flag % may be mixed with any of the others. If an area does not contain
% this flag, then you may not hatch directly into it. There will
% either be a "return channel" provided or you must send your
% submission directly to the FDN head or other listed site.
%
% "&" - Do not send this area to any downlinks. This flag usually
% indicates that an area is a "return channel" to be used for
% submitting files to a FDN head for distribution. Be sure to
% remove it in your TIC.CFG for your uplink *only*. This flag
% should only be used in conjunction with the "*" flag.
%


---

Black Panther
a.k.a. Dan Richter
Sysop - Castle Rock BBS (RCS)
The sparrows are flying again....

--- Mystic BBS v1.12 A36 2017/11/27 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

Hello g00r00,

On 11/28/17, g00r00 said the following...

Since its not even logging anything that implies that either the first word in the file is not "AREA" or the 4th word in the file does not contain a !

The contents of the FSX_FILE.NA that I obtained from the FSXNET.ZIP file
dated Nov 29 2017 is:

% ========================================================================
% FSXNet Fileecho List
% ========================================================================
%
% ------------------------------------------------------------------------
% File Echo Description
% ------------------------------------------------------------------------
%
%
Area FSX_NODE 0 Weekly Nodelists (fsxNet, etc.)
Area FSX_INFO 0 Weekly Infopacks (fsxNet, etc.)
Area FSX_MYST 0 Mystic BBS Software
Area FSX_MUTL 0 Mystic BBS Utils, Mods etc.
Area FSX_SOFT 0 BBS Software (Current + Legacy)
Area FSX_UTLS 0 BBS Utils, Tools, Networking etc.
Area FSX_DOOR 0 BBS Doors, Games etc.
Area FSX_ARTS 0 ANSI Art - Groups, Individuals etc.
%
% End of FSXNet Fileecho List

As you mentioned I see no "!" used in the file. Am I safe to manually add the missing !'s to make the area lines read:

Area FSX_NODE 0 ! Weekly Nodelists (fsxNet, etc.)



Jeff

--- Mystic BBS v1.12 A36 2017/11/26 (Linux/64)
* Origin: New Mystic BBS (21:1/128.3)

Area FSX_NODE 0 ! Weekly Nodelists (fsxNet, etc.)
etc...

I think all you need to add is the exclamation point (!) between the 0
and the description of the file echo. It just indicates that these areas have filebone distribution.

Yep that format looks correct above. I've updated the filebone importer to
log when AREA or ! is not set in a line.

--- Mystic BBS v1.12 A36 2017/11/27 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

As you mentioned I see no "!" used in the file. Am I safe to manually
add the missing !'s to make the area lines read:

Area FSX_NODE 0 ! Weekly Nodelists (fsxNet, etc.)

Yes, that should get it to work! :)

--- Mystic BBS v1.12 A36 2017/11/27 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Hello Avon,

On 11/29/17, Avon said the following...

I should test this also seeing I created it :) It was based on an
othernet file so I expected it to work.. Humm..
You can find it in any fsxNet infopack..if somethings amiss, I'm happy to change it.

I hadn't setup any file areas in Mystic yet and grabbed the FSXNET file from Agency BBS. I took the acquired FSX_FILE.NA ans added a "!" to each area specification to make each line read:

Area FSX_NODE 0 ! Weekly Nodelists (fsxNet, etc.)

After running the [Import_FILEBONE.NA] task again MUTIL reported:

----------------- MUTIL v1.12 A36 2017/11/26 Wed, Nov 29 2017 (loglevel 3)
+ Nov 29 02:03:49 Startup using fsx-file-na.ini
- Nov 29 02:03:49 EXEC Import_FILEBONE.NA
+ Nov 29 02:03:49 Process: Import FILEBONE.NA
+ Nov 29 02:03:49 Weekly Nodelists (fsxNet, etc.)
+ Nov 29 02:03:49 Weekly Infopacks (fsxNet, etc.)
+ Nov 29 02:03:49 Mystic BBS Software
+ Nov 29 02:03:49 Mystic BBS Utils, Mods etc.
+ Nov 29 02:03:49 BBS Software (Current + Legacy)
+ Nov 29 02:03:49 BBS Utils, Tools, Networking etc.
+ Nov 29 02:03:49 BBS Doors, Games etc.
+ Nov 29 02:03:49 ANSI Art - Groups, Individuals etc.
+ Nov 29 02:03:49 Results: Created 5 base(s) in 0.03s
+ Nov 29 02:03:49 Shutdown Normal (0)

Which looks much better. :-)


Jeff

--- Mystic BBS v1.12 A36 2017/11/26 (Linux/64)
* Origin: New Mystic BBS (21:1/128.3)

Hello g00r00,

On 11/28/17, g00r00 said the following...

Since its not even logging anything that implies that either the first word in the file is not "AREA" or the 4th word in the file does not contain a !

I manually added the missing !'s to the existing FSX_FILE.NA file that I had used and after task execution the MUTIL log reported:

----------------- MUTIL v1.12 A36 2017/11/26 Wed, Nov 29 2017 (loglevel 3)
+ Nov 29 02:03:49 Startup using fsx-file-na.ini
- Nov 29 02:03:49 EXEC Import_FILEBONE.NA
+ Nov 29 02:03:49 Process: Import FILEBONE.NA
+ Nov 29 02:03:49 Weekly Nodelists (fsxNet, etc.)
+ Nov 29 02:03:49 Weekly Infopacks (fsxNet, etc.)
+ Nov 29 02:03:49 Mystic BBS Software
+ Nov 29 02:03:49 Mystic BBS Utils, Mods etc.
+ Nov 29 02:03:49 BBS Software (Current + Legacy)
+ Nov 29 02:03:49 BBS Utils, Tools, Networking etc.
+ Nov 29 02:03:49 BBS Doors, Games etc.
+ Nov 29 02:03:49 ANSI Art - Groups, Individuals etc.
+ Nov 29 02:03:49 Results: Created 5 base(s) in 0.03s
+ Nov 29 02:03:49 Shutdown Normal (0)

Which looks much better. I report as much to Avon.

But that raises another question. :-)

Currently when importing either echo or file areas via an NA file the areas
get imported with the area description being used as such:

Base Name Weekly Infopacks (fsxNet, etc.)
FTP Name Weekly_Infopacks_(fsxNet,_etc.)
Echo Tag FSX_INFO

Is it possible to import the areas with the "Echo Tag specification used
also for Ftp Name, and Base Name?

On another Mystic machine when I import echo areas I did this by editing the
NA file to display

Echo Tag Echo Tag

instead of the default

Echo Tag Area Description

I understand this isn't a real problem with Fsxnet given the number of echo/file areas. But when dealing with Fido areas I spend time trying to
choose an area by trying to remember what description is associated with it.


Jeff

--- Mystic BBS v1.12 A36 2017/11/26 (Linux/64)
* Origin: New Mystic BBS (21:1/128.3)

On 11/29/17, Jeffs pondered and said...

I hadn't setup any file areas in Mystic yet and grabbed the FSXNET file from Agency BBS. I took the acquired FSX_FILE.NA ans added a "!" to each area specification to make each line read:

Area FSX_NODE 0 ! Weekly Nodelists (fsxNet, etc.)

Does the ! need to be a certain column Jeff?

--- Mystic BBS v1.12 A36 2017/11/26 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

But that raises another question. :-)

Currently when importing either echo or file areas via an NA file the areas get imported with the area description being used as such:

Is it possible to import the areas with the "Echo Tag specification used also for Ftp Name, and Base Name?

Done. This will be in the next pre-alpha.

--- Mystic BBS v1.12 A36 2017/11/29 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/28/17, Black Panther pondered and said...

It should be in the format of:
Area FSX_NODE 0 ! Weekly Nodelists (fsxNet, etc.)
etc...

I think all you need to add is the exclamation point (!) between the 0
and the description of the file echo. It just indicates that these areas have filebone distribution.

snip<=-

Thanks for this info Dan and also to Jeff for testing the file. I have
tonight updated the file according to the specs Dan provided and it should be available for testing in the next hatched infopack due out in around 6-7
hours time (4am Fri NZDST) from when I compose this reply...

Off to zzzzz. now :)

Best, Paul

--- Mystic BBS v1.12 A36 2017/11/26 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Nugax,

On 11/28/17, Nugax said the following...

What's the na file look like

It's supposed to look like:

Area FSX_NODE 0 ! Weekly Nodelists (fsxNet, etc.)
Area FSX_INFO 0 ! Weekly Infopacks (fsxNet, etc.)
Area FSX_MYST 0 ! Mystic BBS Software
Area FSX_MUTL 0 ! Mystic BBS Utils, Mods etc.
Area FSX_SOFT 0 ! BBS Software (Current + Legacy)
Area FSX_UTLS 0 ! BBS Utils, Tools, Networking etc.
Area FSX_DOOR 0 ! BBS Doors, Games etc.
Area FSX_ARTS 0 ! ANSI Art - Groups, Individuals etc.

Sincerely,
Jon Justvig

---

Sincerely,
Jon Justvig

--- Mystic BBS v1.12 A36 2017/11/27 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (21:1/154)