Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages! You are not logged in. Login here for full access privileges. |
Previous Message | Next Message | Back to Mystic BBS <-- <--- | Return to Home Page |
|
||||||
From | To | Subject | Date/Time | |||
nospam.g00r00 | All | Re: A37 linux .bsy file issue with mutil |
December 15, 2017 3:32 PM * |
|||
RF> again. That said, I'm using mis2, with a36, as it includes an ssh RF> server...is this unsupported? Well you can do whatever you want But I can't support a mix and match of old versions of Mystic that may or may not be compatible with each other, have known issues, etc. A36 doesn't even have a MIS2 so I don't know what you're actually using lol. I get that you also need a working BBS too, so I understand why you're back to the old version. But I can't address or help or resolve anything if I don't have the person who has the problem around to help me. I can't send you a new binary with a fix if you're not at the current release level, etc. RF> DOSEMU was not complaining about security, in fact none of the RF> complaints were related to security or ownership. DOSEMU complained RF> about not being able to figure out character sets (cp437, auto, us, etc) I'm not super familiar with DOSEMU but if the error is that it can't read its configuration to get the default character set, then I would think that could be very possibly be related to security. Most earlier copies of test-release MIS2 (before it had all of the servers fully functional) had an issue where in some cases it wasn't dropping its root access after port binding... If you happen to build and test your BBS with that server exclusively, and then switch to the "stable" version which doesn't have that issue, I think it would cause all sorts of random shit to go wrong. As far as the BSY files, the FSXNET hub gets hammered and really tests this stuff hard. There are times when all 16 incoming BINKP nodes are active at once receiving mail while there is also outbound BINKP and echomail tossing all happening in harmony... My point is that if it was a general issue like BSY files not getting deleted, then the entire network would halt within minutes of deploying the server. Thee would also be a LOT of people reporting the same issue, and so far its only you. The only other commonality between being unable to delete a BSY file and a piece of software not reading its configuration values in my mind, would be something with security either on the admin side or the software side. --- SoupGate-Win32 v1.05 * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3) |
||||||
|
Previous Message | Next Message | Back to Mystic BBS <-- <--- | Return to Home Page |
Execution Time: 0.0905 seconds If you experience any problems with this website or need help, contact the webmaster. VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved. Virtual Advanced Copyright © 1995-1997 Roland De Graaf. |