Synchronet requires prerequisites. If you missed any of those, it won't install. Otherwise, if you follow the wiki for installing on Linux, it compiles just fine on just about anything.
Yes it compiles fine. But when i first executed it, it wanted to open lots of TCP/IP ports, even on closed services. The Pi don't liked that...
At that time i don't go further. I've choice between the two software.
No offense, and maybe it's a language barrier, but when you come to a public forum about said software and say that two separate softwares "don't work", even though there's hundreds of working systems around the world using these two softwares, it makes people think that the problem isn't the software.
Yeah, in such cases it's usually good to try to figure out what's wrong
in the setup, ask for help if needed, and try to fix things..
Mystic do strange things on Pi. Now is on Event config. I do some modifications to one event and after some time, this event resets alone
to the old values.
Same problem here. Also sometimes ignores stacked commands. Turning on
the ./ prefix doesn't work. I just put it in the command line. Also
the node setup ignores whats in the echomail in and out folder setting
and uses the default.
Mystic do strange things on Pi. Now is on Event config. I do some modifications to one event and after some time, this event resets alone
to the old values.
Same problem here. Also sometimes ignores stacked commands. Turning on
the ./ prefix doesn't work. I just put it in the command line. Also
the node setup ignores whats in the echomail in and out folder setting
and uses the default.
A bug that a have but now it seen to be OK, is on "message Base Editor"
on echomail Bases the option "Export To"
lost this setting
Mystic do strange things on Pi. Now is on Event config. I do somemodifications to one event and af
ter some time, this event resets alone to
the old values.
Make sure the BBS is down when you make changes like this. I know, it's annoying lol.
The problem is, Mystic/MIS doesn't tell you when this needs to be done
(it probably should), and doesn't /always/ require it. So, the "recommendation" has always been that whenever you make changes in Mystic's configuration, you should restart MIS afterwards.
A bug that a have but now it seen to be OK, is on "message Base Editor"
on echomail Bases the option "Export To" lost this setting and
goes to "0 node". I've to verify (various times) all echomail Bases to
see is this setting is good to "1 node".
| Sysop: | Tetrazocine |
|---|---|
| Location: | Melbourne, VIC, Australia |
| Users: | 15 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 255:16:02 |
| Calls: | 218 |
| Files: | 21,503 |
| Messages: | 85,134 |