Lastest package A31 (I did copy message base files from a19 but I didnt see any changes to the files in updates...)
--- Mystic BBS v1.12 A31 (Linux)
* Origin: -=-CyberNet BBS | Home of Cyber-Net -=- (21:1/107)
On 10/04/16, Varsuchi said the following...
Lastest package A31 (I did copy message base files from a19 but I didnt see any changes to the files in updates...)
--- Mystic BBS v1.12 A31 (Linux)
* Origin: -=-CyberNet BBS | Home of Cyber-Net -=- (21:1/107)
I remember having to run update on the data files at least when going from >a19 to A20's and then again a few times in the 20's. I think it stayed the >same from A29 thru A31. Really have to look at the upgrade text g00r00 puts >with them.
I don't remember anything with msgs themselves so if that's all you copied, >then that's not it. Could be the big number of connections, I've never tried >anything over 8 myself (remember it's Alpha not release).
--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
Varsuchi wrote to All <=-
Concerns me though, cause you cannot simply backup your message files
and move to latest mystic.
It was the message files. Removed them and all is well. I never saw anything about those.
Concerns me though, cause you cannot simply backup your message files and move to latest mystic.
bcw142 wrote to Varsuchi <=-
On 10/04/16, Varsuchi said the following...
It was the message files. Removed them and all is well. I never saw anything about those.
Concerns me though, cause you cannot simply backup your message files and move to latest mystic.
Odd. When I upgrade I generally recreate the setups and then use
AreaFix and %RESCAN to get the messages back. So then they came in
under the new setup.
--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 2 |
Nodes: | 8 (0 / 8) |
Uptime: | 92:25:59 |
Calls: | 2,122 |
Calls today: | 3 |
Files: | 11,149 |
D/L today: |
48 files (22,099K bytes) |
Messages: | 950,672 |