Hi DM,
For the Loadable Modules configuration in SCFG, it seems it doesn't accept full/relative paths, is that correct?
I've started working on updating my message reader so that it can be used directly as a loadable module (without needing separate loadable module scripts), but one possible issue is that DDMsgReader is under sbbs/xtrn/DDMsgReader (and it's actually one level deeper on my system). I've tried specifying a relative path + DDmsgReader in SCFG, but then Synchronet gave an error saying it couldn't execute it. I also saw that the wiki says only the name of the file is accepted (no .js or .bin file extension) - I assume that also means no path prefix as well? https://wiki.synchro.net/util:scfg:system#loadable_modules
One workaround I thought of was to create another, DDMsgReader.js which one could place in sbbs/mods, which would just build a string of arguments from argv and then call bbs.exec() to run the actual DDMsgReader. Or perhaps DDMsgReader.js could be moved into sbbs/exec, and its config files could be moved to sbbs/ctrl etc., but it seems cleaner to have all of its files together under /xtrn/DDMsgReader.
It's a mix. Have you looked at the online (F1) help? It clarifies which loadable modules use full command-lines are which are just module names.
For the Loadable Modules configuration in SCFG, it seems it doesn't
accept full/relative paths, is that correct?
It's a mix. Have you looked at the online (F1) help? It clarifies which loadable modules use full command-lines are which are just module names.
One workaround I thought of was to create another, DDMsgReader.js
which one could place in sbbs/mods, which would just build a string of
arguments from argv and then call bbs.exec() to run the actual
DDMsgReader. Or perhaps DDMsgReader.js could be moved into sbbs/exec,
and its config files could be moved to sbbs/ctrl etc., but it seems
cleaner to have all of its files together under /xtrn/DDMsgReader.
Yup, either of those seem like viable workarounds.
It's a mix. Have you looked at the online (F1) help? It clarifies
which loadable modules use full command-lines are which are just
module names.
The wiki page also states which is which (they're separate tables). But he wants to force the path even on the ones that accept parameters, which AFAIK he can't do.
Re: Loadable Modules and full/relative paths
By: Digital Man to Nightfox on Tue Mar 08 2022 07:32 pm
For the Loadable Modules configuration in SCFG, it seems it doesn't
accept full/relative paths, is that correct?
It's a mix. Have you looked at the online (F1) help? It clarifies which loadable modules use full command-lines are which are just module names.
I've had a look. Does "full command-line" include a leading path, or does that just mean it can take command-line parameters?
One workaround I thought of was to create another, DDMsgReader.js
which one could place in sbbs/mods, which would just build a string of
arguments from argv and then call bbs.exec() to run the actual
DDMsgReader. Or perhaps DDMsgReader.js could be moved into sbbs/exec,
and its config files could be moved to sbbs/ctrl etc., but it seems
cleaner to have all of its files together under /xtrn/DDMsgReader.
Yup, either of those seem like viable workarounds.
I suppose that will suffice.
| Sysop: | Nelgin |
|---|---|
| Location: | Plano, TX |
| Users: | 606 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 97:39:28 |
| Calls: | 9,601 |
| Calls today: | 1 |
| Files: | 16,056 |
| D/L today: |
2 files (57K bytes) |
| Messages: | 1,061,229 |