Hi, all -

When I add a message area and try to save, I'm getting errors similar to the following on 10 areas, all in different file libraries:

!ERROR 22 (Invalid argument) creating directory: c:\sbbs\data\dirs\fsxnet\c:\sbbs\data\dirs\fsxnet\fsx_node

The definitions for the libraries and areas throwing errors look fine:

+[Ý][?]----------------------------------------------------+
Ý fsxnet Library Ý Ý----------------------------------------------------------Ý
Ý ÝLong Name Network - FSXNet Ý
Ý ÝShort Name fsxnet Ý
Ý ÝInternal Code Prefix Ý
Ý ÝParent Directory c:\sbbs\data\dirs\fsxnet Ý
Ý ÝAccess Requirements LEVEL 50 Ý
Ý ÝAccess to Sub-directories No Ý
Ý ÝSort Library By Directory Index Position Ý
Ý ÝClone Options Ý
Ý ÝExport Areas... Ý
Ý ÝImport Areas... Ý
Ý ÝFile Directories... Ý +----------------------------------------------------------+


+[Ý][?]----------------------------------------------------------+
Ý FSX_NODE Directory Ý Ý----------------------------------------------------------------Ý
Ý ÝLong Name Weekly Nodelists (fsxNet, etc.) Ý
Ý ÝShort Name FSX_NODE Ý
Ý ÝInternal Code FSX_NODE Ý
Ý ÝAccess Requirements LEVEL 50 Ý
Ý ÝUpload Requirements Ý
Ý ÝDownload Requirements Ý
Ý ÝOperator Requirements Ý
Ý ÝExemption Requirements Ý
Ý ÝTransfer File Path c:\sbbs\data\dirs\fsxnet\fsx_node\ Ý
Ý ÝMaximum Number of Files 10000 Ý
Ý ÝPurge by Age Disabled Ý
Ý ÝCredit on Upload 100% Ý
Ý ÝCredit on Download 90% Ý
Ý ÝToggle Options... Ý
Ý ÝAdvanced Options... Ý +----------------------------------------------------------------+

And when I look in file.cnf I can't find the doubled path anywhere in the file.

Any suggestions?

Thanks,

Kurt

---
þ Synchronet þ realitycheckBBS -- http://realitycheckBBS.org

Re: Problem with file areas
By: poindexter FORTRAN to All on Wed May 08 2019 12:26:00

!ERROR 22 (Invalid argument) creating directory: c:\sbbs\data\dirs\fsxnet\c:\sbbs\data\dirs\fsxnet\fsx_node

Ý ÝParent Directory c:\sbbs\data\dirs\fsxnet Ý

Ý ÝTransfer File Path c:\sbbs\data\dirs\fsxnet\fsx_node\ Ý

At a guess I'd say that the transfer file path needs to be relative to the parent directory, if a parent directory is specified. (That's my interpretation of this error paired with this configuration anyway.)

---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-425-5435
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

When I add a message area and try to save, I'm getting errors similar to the following on 10 areas, all in different file libraries:

!ERROR 22 (Invalid argument) creating directory: c:\sbbs\data\dirs\fsxnet\c:\sbbs\data\dirs\fsxnet\fsx_node

The definitions for the libraries and areas throwing errors look fine:

ÿ ÿParent Directory c:\sbbs\data\dirs\fsxnet ÿ

ÿ ÿTransfer File Path c:\sbbs\data\dirs\fsxnet\fsx_node\ ÿ

Your parent directory is already defined. Just enter fsx_node\ for the transfer
path.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Problem with file areas
By: echicken to poindexter FORTRAN on Wed May 08 2019 03:53 pm

Re: Problem with file areas
By: poindexter FORTRAN to All on Wed May 08 2019 12:26:00

!ERROR 22 (Invalid argument) creating directory: c:\sbbs\data\dirs\fsxnet\c:\sbbs\data\dirs\fsxnet\fsx_node

Ý ÝParent Directory c:\sbbs\data\dirs\fsxnet Ý

Ý ÝTransfer File Path c:\sbbs\data\dirs\fsxnet\fsx_node\ Ý

At a guess I'd say that the transfer file path needs to be relative to the parent directory, if a parent directory is specified. (That's my interpretation of this error paired with this configuration anyway.)

Yup, that's right. The Transfer File Path is relative to the (optional) library parent directory. Absolute paths in both won't work.

digital man

Synchronet/BBS Terminology Definition #1:
ANSI = American National Standards Institute
Norco, CA WX: 62.8øF, 72.0% humidity, 4 mph SE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Problem with file areas
By: Digital Man to echicken on Wed May 08 2019 01:39 pm

Yup, that's right. The Transfer File Path is relative to the (optional) library parent directory. Absolute paths in both won't work.

That did it - thanks!

---
þ Synchronet þ realitycheckBBS -- http://realitycheckBBS.org