Hi!
I am curious about the best/quickest/easiest way to shuffle some message boards around to re-organize the groups on my system.
Unfortunately, it seems that the message group internal code prefix kind of gets in the way, and SCFG doesn't take a board's
messages and shuffle everything around that it needs to when one cuts & pastes.
I don't see any option in smbutil to export the messages from one base (which I presume one might be able to then pipe through to
smbutil for import to another), so, I'm kind of confused.
Am I overthinking something really obvious, or is this trickier than I'm thinking it should be?
boards around to re-organize the groups on myI am curious about the best/quickest/easiest way to shuffle some message
<new_intcode>.*.system.
Just rename (e.g. from a command prompt) data/subs/<old_intcode>.* to
The internal code (prefix + suffix) determines the base filenames. Justrename them to match the newly created ("moved")
sub-board in SCFG.
Re: Moving board to different group
By: Digital Man to Va7aqd on Sun May 19 2019 09:55 pm
I am curious about the best/quickest/easiest way to shuffle some message boards around to re-organize the groups on my
system.
Just rename (e.g. from a command prompt) data/subs/<old_intcode>.* to <new_intcode>.*.
The internal code (prefix + suffix) determines the base filenames. Just rename them to match the newly created ("moved")
sub-board in SCFG.
It's just that simple, eh? Excellent, thanks! I think I'll draft up a little script to manage the process so that things get backed
up, renamed without overwriting anything (or from fat-fingering), etc.
Va7aqd wrote to Digital Man <=-b
I am curious about the best/quickest/easiest way to shuffle some message
oards around to re-organize the groups on my<new_in
system.
Just rename (e.g. from a command prompt) data/subs/<old_intcode>.* to
tcode>.*.renam
The internal code (prefix + suffix) determines the base filenames. Just
e them to match the newly created ("moved")
sub-board in SCFG.
It's just that simple, eh? Excellent, thanks! I think I'll draft
up a little script to manage the process so that things get
backed up, renamed without overwriting anything (or from
fat-fingering), etc.
up, renamed without overwriting anything (or from fat-fingering), etc.
I think something went wrong... I had 73 messages this morning in
DoveNet Sysops Only - seems like they are old-ish dupes from the
fsxNet echos...
Re: Re: Moving board to different group
By: Dan Clough to Va7aqd on Tue May 21 2019 09:07 am
I think something went wrong... I had 73 messages this morning in DoveNet Sysops Only - seems like they are old-ish dupes from the
fsxNet echos...
That's interesting - glad I only moved the one production message base so far.
What I did was move the base from one group to another in SCFG via a CTRL-X and then a CTRL-V in the other group. I noticed that
my read msg pointers were reset/unknown for the message base, which I supposed wasn't too unexpected.
I see that after I moved the message base a bunch of messages were sent out to VERT, but only 115 of them.
Not sure why that would occur, and I don't see where I could set the highwater mark for QWK message bases.
Curious why the dupes wouldn't have been destroyed at VERT, too.
Digital Man - any thoughts on how this could be prevented when moving message bases around on a system?
But, without fat fingers, how do you pick up the food and the
silverware?? Even Sysops have to eat. <BG>
I'm not sure what happened in your case. Can you double-check your settingsin SCFG->Networks->QWK->Hubs->VERT->Sub-boards? Make
sure it only includes the DOVE-Net subs (no FSX-GEN).
Re: Re: Moving board to different group
By: Digital Man to Va7aqd on Tue May 21 2019 12:43 pm
I'm not sure what happened in your case. Can you double-check your settings in SCFG->Networks->QWK->Hubs->VERT->Sub-boards? Make
sure it only includes the DOVE-Net subs (no FSX-GEN).
I have no idea how this happened, but your guess was absolutely correct.
The QWK board with Conf # 2010 was FSX_GEN. I know that
I didn't make that particular change myself, and am now curious how that may have occurred via anything else I might have done. Is
it possible that when I took the Dove-Net Sysops Echo and did the ^X on it that it would have altered the QWK Hub Sub-board setting
since the message area may not have technically existed at that point?
I have set the QWK Conf # back to the correct msg base, and I apologise for the mess it might have created on anyone else's system.
I'll keep an eye out for further unexpected changes.
DM, if moving a message base from one group to another has no really simple or sane path in SCFG (without manually checking up on
anything else that might be relevant, manually moving/renaming files, etc.), would it be prudent to put in a feature request to ask
for a proper SCFG message area move option that handles all the possible tie-in problems and file renaming, etc?
and fix it.since the message area may not have technically existed at that point?Something like that. I'll have to play with it and see if I can reproduce
That is the proper way to move a message base from one group to another, itjust needs a fix it sounds like. I don't think
another "move option" is necessary.
Re: Re: Moving board to different group
By: Va7aqd to Digital Man on Tue May 21 2019 11:00 pm
Howdy DM,
I noticed your code changes for SCFG overnight so applied & tested.
The fix does indeed fix the confused QWK net hub conference number getting confused issue, but it now does completely remove the entry from the hub, so a CTRL-X, then CTRL-V on the message area doesn't necessarily work as expected as one has to then go re-add that entry to the QWKnet hub. I suspect it might be nicer for the admin if the data was retained/adjusted accordingly in the QWKnet hub settings if a message area just gets moved in this fashion?
Okay, that should be addressed now too.
getting confused issue, but it now does completely removeThe fix does indeed fix the confused QWK net hub conference number
Okay, that should be addressed now too.
Re: Re: Moving board to different group
By: Digital Man to Va7aqd on Wed May 22 2019 01:12 pm
Okay, that should be addressed now too.
Will give that a run-through very shortly here.
On an off-topic note - the FTN outbox functionality seems to be working just fine. The script that I use for the game involved now does less - it checks for files in that outbox folder still and triggers binkit to call out when it finds them there. BinkIT seems to be dealing with the contents just great.
Re: Re: Moving board to different group
By: Digital Man to Va7aqd on Wed May 22 2019 01:12 pm
The fix does indeed fix the confused QWK net hub conference number getting confused issue, but it now does completely removeOkay, that should be addressed now too.
Seems to be working as expected there now, that's great, thanks again!
One further question - is there a way to move message bases like this without resetting everyone's read message index? I suspect that might be a little more work, but I'm thinking in the future if anything needs to be moved and other users actually exist and are using the system, that could be a little disruptive to lose those read-message highwater marks.
But, without fat fingers, how do you pick up the food and the silverware?? Even Sysops have to eat. <BG>
I have seen many skinny fingers make light work of exercising the silverware V>produce a satisfactory consumption outcome.
And I also hope not all sysop fingers are fat! ;-)
The pointers are stored in data/user/*.subs files and are referenced byinternal code. So if you change a sub's internal code,
you're making everyone's configuration and pointers for that sub invalid. Ascript (or something) would have to walk through all
those *.subs files and rename the sections to match the new internalcode(s). It's not impossible, but not something I'm
currently doing.
Re: Re: Moving board to different group
By: Digital Man to Va7aqd on Wed May 22 2019 07:42 pm
The pointers are stored in data/user/*.subs files and are referenced by internal code. So if you change a sub's internal code,
you're making everyone's configuration and pointers for that sub invalid. A script (or something) would have to walk through all
those *.subs files and rename the sections to match the new internal code(s). It's not impossible, but not something I'm
currently doing.
Sure, yeah, I figured that would likely be somewhat more involved. On the admin side though, generally if one is going to move a sub from one group to another, there's going to be an internal code change, correct? So I believe it's hard to avoid this condition if one wants to re-org their bases at all.
No, not necessarily. If you don't use group internal code prefixes, it'sperfectly reasonable to move a sub from one group to
another and keep the same internal code.
Re: Re: Moving board to different group
By: Digital Man to Va7aqd on Fri May 24 2019 01:00 am
No, not necessarily. If you don't use group internal code prefixes, it's perfectly reasonable to move a sub from one group to
another and keep the same internal code.
Alright... is there any suggested best practise with using or not using group internal code prefixes?
Alright... is there any suggested best practise with using or not
using group internal code prefixes?
I like code prefixes, but not everyone uses them for all message groups.
group internal code prefixes?Alright... is there any suggested best practise with using or not using
I like code prefixes, but not everyone uses them for all message groups.<shrug>
On 05-24-19 14:14, Digital Man wrote to Va7aqd <=-
I like code prefixes, but not everyone uses them for all message
groups. <shrug>
On 05-24-19 14:14, Digital Man wrote to Va7aqd <=-
I like code prefixes, but not everyone uses them for all message groups. <shrug>
I tend to use them, pretty much eliminates the possibility of duplicate internal IDs by default.
On 05-24-19 19:05, Digital Man wrote to Tony Langdon <=-
Yup. It also extends the maximum internal code length from 8 to 16
chars.
Alright... is there any suggested best practise with using or not using group internal code prefixes?
I started using group prefixes for all my message groups when I realizedthat it can be fairly common for different message
networks to have the same name/code for some message areas (such as"general", etc.). And more recently, I've started storing
my messagebase files in a different directory for each message group (thoughI doubt that makes a different for avoiding
cross-posting conflicts).
Re: Re: Moving board to different group
By: Nightfox to Digital Man on Fri May 24 2019 03:49 pm
I started using group prefixes for all my message groups when I realized that it can be fairly common for different message
networks to have the same name/code for some message areas (such as "general", etc.). And more recently, I've started storing
my messagebase files in a different directory for each message group (though I doubt that makes a different for avoiding
cross-posting conflicts).
I have read everyone's further comments on why they're using the group internal prefixes and I agree that it's a nice feature to have in there. For my purposes, as I'm grouping echos not by Network, but by categories, and since there is no current function in Synchro to move properly without destroying everyone's highwater marks, it seems that I'm going to have to remove the group internal prefix and manage the rest of the internal coding closely, to avoid the duplicates from networks, etc.
How many times are you going to be moving/re-arranging sub-boards? Seemslike a one-time task.
Re: Re: Moving board to different group
By: Digital Man to Va7aqd on Tue May 28 2019 02:50 pm
How many times are you going to be moving/re-arranging sub-boards? Seems like a one-time task.
I wouldn't expect very often, but perhaps as things evolve and grow on the system (I'm an optimist, I know). If today I have one echo that currently falls in with a more generalized group, but then in 6 months or 5 years I have 5 similar-ish echos that deserve their own group, I should be able to move them without having to think too much about it, no?
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 25 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 37:49:15 |
| Calls: | 1,890 |
| Calls today: | 1 |
| Files: | 11,074 |
| Messages: | 932,929 |