you may remember me mentioning a time or two about something creating
all my file library directories in my ctrl directory... i've found that
scfg does this... research incomming...
Have you tried starting the board in the exec directory to see if that solves the issue?
Hope this helps
you may remember me mentioning a time or two about something creating all my file library directories in my ctrl directory... i've found that scfg does this... research incomming...
[time passes]
scfg is trying to create these directories when i go to exit the file area config... i just made a change to a template area's Advanced Options Data Directory and cloned it to all the other areas in that library... i added a '/' to the beginning of that field because i noticed that the transfer file path is calculated from
the library's Parent Directory
the directory's Advanced Options Data Directory
and the directory's Internal Code
it appears that scfg is trying to create the Advanced Options Data Directories in the root directory but it can't... it looks like it is not taking the library's Parent Directory into account... so when it is trying to create these
directories, it is currently returning an error 13 permission denied because of
that leading '/' i just put in...
[time passes]
yup! that's exactly what the problem is... without the leading slash, the directories are all created in the current directory and since i'm always starting in /sbbs/ctrl, guess where scfg creates all of them? the funny thing is that the BBS itself uses the proper ones in /sbbs/data/dirs...
maybe i'm doing something wrong, though...
plus i have another problem where moving areas to a new library also do not work as desired but that's for another time... right now i need to fix 370someodd areas so this will stop and i can get them all rearranged into the new library layout i'm trying to work on...
)\/(ark
you may remember me mentioning a time or two about something creating all my file library directories in my ctrl directory... i've found that scfg does this... research incomming...
[time passes]
scfg is trying to create these directories when i go to exit the file area config... i just made a change to a template area's Advanced Options Data Directory and cloned it to all the other areas in that library... i added a '/' to the beginning of that field because i noticed that the transfer file path is calculated from
the library's Parent Directory
the directory's Advanced Options Data Directory
and the directory's Internal Code
it appears that scfg is trying to create the Advanced Options Data Directories in the root directory but it can't... it looks like it is not taking the library's Parent Directory into account...
so when it is trying
to create these directories, it is currently returning an error 13 permission denied because of that leading '/' i just put in...
[time passes]
yup! that's exactly what the problem is... without the leading slash, the directories are all created in the current directory and since i'm always starting in /sbbs/ctrl, guess where scfg creates all of them? the funny thing is that the BBS itself uses the proper ones in /sbbs/data/dirs...
maybe i'm doing something wrong, though...
the problem is that the file directories and data files properly exist in /sbbs/data/dirs but scfg creates the directories in /sbbs/ctrl when it should not... this is a bug report not a "help me, my board can't find the file areas" report ;)
you may remember me mentioning a time or two about something creating
all my file library directories in my ctrl directory... i've found that
scfg does this... research incomming...
Doesn't ring a bell.
The library's parent directory has nothing to do with the data storage directory. The help (F1 key) output from SCFG for that option:
Parent Directory:
This an optional path to be used as the physical "parent" directory for all logical directories in this library. This parent directory will be used in combination with each directory's storage path to create the
full physical storage path for files in this directory.
Transfer File Path [../data/dirs/fdist-dailylis/]Maximum Number of Files 10000
This option is convenient for adding libraries with many directories
that share a common parent directory (e.g. CD-ROMs) and gives you the option of easily changing the common parent directory location later, if desired.
... says nothing about the data storage.
yup! that's exactly what the problem is... without the leading slash,
the directories are all created in the current directory and since i'm
always starting in /sbbs/ctrl, guess where scfg creates all of them? the
funny thing is that the BBS itself uses the proper ones in
/sbbs/data/dirs...
maybe i'm doing something wrong, though...
It sounds like you're confusing the file storage path with the data directory. Just leave the data directory blank (the default) - I doubt that's what you want to be actually changing.
the problem is that the file directories and data files properly exist
in /sbbs/data/dirs but scfg creates the directories in /sbbs/ctrl when
it should not... this is a bug report not a "help me, my board can't
find the file areas" report ;)
I don't think there's any bug here. I fully expect that if you set a
file directory's advanced -> data directory to a relative path (one
that doesn't start with "/"), that the directory would be created
relative to your "ctrl" directory. It sounds like it's behaving
exactly as I would expect.
On 2019 Jul 12 13:19:50, you wrote to me:
you may remember me mentioning a time or two about something creating
all my file library directories in my ctrl directory... i've found that
scfg does this... research incomming...
Doesn't ring a bell.
yeah, it was back in sept 2018 when i first installed...
The library's parent directory has nothing to do with the data storage directory. The help (F1 key) output from SCFG for that option:
yeah, i read the F1 help... it made some sense to a point...
Parent Directory:
This an optional path to be used as the physical "parent" directory for all logical directories in this library. This parent directory will be used in combination with each directory's storage path to create the full physical storage path for files in this directory.
"storage path" == "transfer path" in the interface?? in other words, is this the storage path?
Exemption Requirements
Transfer File Path [../data/dirs/fdist-dailylis/]Maximum Number of Files 10000
This option is convenient for adding libraries with many directories that share a common parent directory (e.g. CD-ROMs) and gives you the option of easily changing the common parent directory location later, if desired.
yes, i think i want to use that with the filegate file distribution stuff... i was looking to separate the directories into better categories...
... says nothing about the data storage.
it was empirical based on observation... i don't need to move the databases but i thought keeping them with the file areas' libraries might be a good idea... i'm backing off on that thought, though...
yup! that's exactly what the problem is... without the leading slash,
the directories are all created in the current directory and since i'm
always starting in /sbbs/ctrl, guess where scfg creates all of them? the
funny thing is that the BBS itself uses the proper ones in
/sbbs/data/dirs...
maybe i'm doing something wrong, though...
It sounds like you're confusing the file storage path with the data directory. Just leave the data directory blank (the default) - I doubt that's what you want to be actually changing.
i wasn't confusing them, though... i'm trying to keep the ctrl directory from having all the file storage/transfer directories created in it... it happens every single time i go into the file areas and save any changes... i don't recall if it happened before i imported the NA files for the file areas i carry in fidonet or not... either way, hundreds of directories are created in ctrl and i have to manually delete them every single time...
i'll post another message in this thread with my actual settings...
"storage path" == "transfer path" in the interface?? in other words, is
this the storage path?
Correct.
yes, i think i want to use that with the filegate file distribution
stuff... i was looking to separate the directories into better
categories...
You can do that without changing where the data files are stored.
reference... says nothing about the data storage.
it was empirical based on observation... i don't need to move the
databases but i thought keeping them with the file areas' libraries
might be a good idea... i'm backing off on that thought, though...
It's preferable to keep your database and the files to which they
in separate locations. Otherwise you end up with all kinds of weird issues with addfiles and such.
i'll post another message in this thread with my actual settings...
Okay, hopefully that clarify the matter.
On 2019 Jul 12 13:23:04, you wrote to me:
the problem is that the file directories and data files properly exist
in /sbbs/data/dirs but scfg creates the directories in /sbbs/ctrl when
it should not... this is a bug report not a "help me, my board can't
find the file areas" report ;)
I don't think there's any bug here. I fully expect that if you set a file directory's advanced -> data directory to a relative path (one that doesn't start with "/"), that the directory would be created relative to your "ctrl" directory. It sounds like it's behaving
exactly as I would expect.
i really hope that's not the case cause it is not creating them relatively...
the following settings are identical in all my filegate file distribution areas... the only thing that is different between each one is the last directory listed in the "Transfer File Path"... it is apparently generated from "Parent Directory", "Internal Code Prefix" and "Short Name"... at least, that's what it looks like visually...
if i change "Access to Sub-directories" to "Yes" and then immediately back to "No", exiting the file area definitions asks if i want to save changes... if i say yes, all these directories are created in ctrl... i have tried being in /sbbs/tmp and running scfg from there and the directories are
still created in ctrl...
"Parent Directory", "Transfer File Path" and "Data Directory" are blank fields in my configuration and have been since installation...
File Dist Net Library
Long Name File Distribution Network
Short Name File Dist Net
Internal Code Prefix FDIST-
Parent Directory
Access Requirements
Access to Sub-directories No
Sort Library By Directory Index Position
Clone Options
Export Areas...
Import Areas...
File Directories...
DAILYLIST Directory
Long Name ADM: Daily Fidonet Nodelist
Short Name DAILYLIST
Internal Code FDIST-DAILYLIS
Access Requirements
Upload Requirements
Download Requirements
Operator Requirements
Exemption Requirements
Transfer File Path [../data/dirs/fdist-dailylis/]
Maximum Number of Files 10000
Purge by Age Disabled
Credit on Upload 0%
Credit on Download 0%
Toggle Options...
Advanced Options...
Advanced Options
Extensions Allowed
Data Directory [../data/dirs/]
Upload Semaphore File
Sort Value and Direction Name Ascending
Directory Index Now 20 / Was 20
[trim config screens]
I don't see anything obviously wrong.
yeah, me either... that's why it is so annoying...
I assume what you're saying is that SCFG is creating a directory of "ctrl/fdist-dailysis" when you save changes?
exactly!
i really hope that's not the case cause it is not creating them
relatively...
Yes, yes the are - relative to the "ctrl" directory.
the following settings are identical in all my filegate file
distribution areas... the only thing that is different between each one
is the last directory listed in the "Transfer File Path"... it is
apparently generated from "Parent Directory", "Internal Code Prefix"
and "Short Name"... at least, that's what it looks like visually...
The "Short Name" is not used for paths, the internal code suffix is.
configif i change "Access to Sub-directories" to "Yes" and then immediately
back to "No", exiting the file area definitions asks if i want to save
changes... if i say yes, all these directories are created in ctrl... i
have tried being in /sbbs/tmp and running scfg from there and the
directories are still created in ctrl...
Yes, that would be expected because of this line in scfg.c:
if(chdir(cfg.ctrl_dir)!=0) {
printf("!ERROR %d changing current directory to: %s\n"
,errno,cfg.ctrl_dir);
exit(-1);
}
Since the BBS runs with the "ctrl" directory as the cwd, so does the
program (SCFG). Changing the cwd before running cwd (or sbbs) won'tmatter.
I don't see anything obviously wrong.
I assume what you're saying is that SCFG is creating a directory of "ctrl/fdist-dailysis" when you save changes?
That certainly doesn't look like that should be the case.
I assume what you're saying is that SCFG is creating a directory of
"ctrl/fdist-dailysis" when you save changes?
exactly!
If you go to the file transfer section of your BBS, change to the this "fdist-dailysys" directory and then use the ;DIR sysop command, what directory does it say it's listing?
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 28 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 190:27:19 |
| Calls: | 2,005 |
| Calls today: | 2 |
| Files: | 11,114 |
| Messages: | 942,285 |