However under "mystic/echomail/out/primary/" I only see "00010064.clo". The 00000383.we0 file, which presumably holds the actual message isn't there
Warpslide wrote to Gluon <=-
However under "mystic/echomail/out/primary/" I only see "00010064.clo". The 00000383.we0 file, which presumably holds the actual message isn't there
Two things you can try.
Install the zip & unzip packages:
sudo apt install zip unzip
Or remove the Archive Type from the node entry under Echomail Nodes in mystic -cfg.
I followed Avon's video tutorials on how to setup Mystic for the
Raspberry Pi but I'm having a small issue when trying to send echomail out. Actually, the problem occurs when exporting echomail.
Alpha wrote to Gluon <=-
I followed Avon's video tutorials on how to setup Mystic for the
Raspberry Pi but I'm having a small issue when trying to send echomail out. Actually, the problem occurs when exporting echomail.
Do you have ZIP installed, and in your path if it's Windows? that got
me last time :)
I followed Avon's video tutorials on how to setup Mystic for the
Raspberry Pi but I'm having a small issue when trying to send
echomail out. Actually, the problem occurs when exporting echomail.
- May 20 13:05:17 EXEC: zip -qj9 /home/gluon/var/bbs/mystic/echomail/out/primary/00000383.we0 /home/gluon/var/bbs/mystic/temputil/0c33a75f.pkt
+ May 20 13:05:17 Adding PKT to FLO (addr=21:1/100 pkt=/home/gluon/var/bbs/mystic/echomail/out/primary/00000383.we0 flo=/home/gluon/var/bbs/mystic/echomail/out/primary/00010064.clo)
vorlon wrote to Gluon <=-
I followed Avon's video tutorials on how to setup Mystic for the
Raspberry Pi but I'm having a small issue when trying to send
echomail out. Actually, the problem occurs when exporting echomail.
- May 20 13:05:17 EXEC: zip -qj9 /home/gluon/var/bbs/mystic/echomail/out/primary/00000383.we0 /home/gluon/var/bbs/mystic/temputil/0c33a75f.pkt
+ May 20 13:05:17 Adding PKT to FLO (addr=21:1/100 pkt=/home/gluon/var/bbs/mystic/echomail/out/primary/00000383.we0 flo=/home/gluon/var/bbs/mystic/echomail/out/primary/00010064.clo)
As others have already said, you didn't have zip/unzip installed, but
why not go one better and not even bother with them and use raw *.pkt files? It's not like we are all on dialup these days.
To do that set no compression option for the nodes in your config.
Gluon wrote to vorlon <=-
Yeah, that's a good idea, especially on a Raspberry Pi with a humble
CPU. On the other hand it means more I/O on the SD card. I'll see what works best. Thanks.
On 05-21-20 11:03, Gluon wrote to vorlon <=-
To do that set no compression option for the nodes in your config.
Yeah, that's a good idea, especially on a Raspberry Pi with a humble
CPU. On the other hand it means more I/O on the SD card. I'll see what works best. Thanks.
Warpslide wrote to Gluon <=-
Gluon wrote to vorlon <=-
Yeah, that's a good idea, especially on a Raspberry Pi with a humble
CPU. On the other hand it means more I/O on the SD card. I'll see what works best. Thanks.
If I'm setting something up to run for the long term, I usually set it
to boot from a hard drive or USB flash drive instead of the SD card. I was so surprised to see how much faster the Pi performs when it's not limited by the speed of the SD card. The Pi4 doesn't have direct boot
to USB just yet, but I've set it up to boot to the SD card and then
hand it off to a 200GB PiDrive I have.
Vk3jed wrote to Gluon <=-
On 05-21-20 11:03, Gluon wrote to vorlon <=-
To do that set no compression option for the nodes in your config.
Yeah, that's a good idea, especially on a Raspberry Pi with a humble
CPU. On the other hand it means more I/O on the SD card. I'll see what works best. Thanks.
Really? Why? Compressing from *.pkt to arcmail bundles causes a fair
bit of I/O.
Yeah, that's a good idea, especially on a Raspberry Pi with a humble
CPU. On the other hand it means more I/O on the SD card. I'll see what works best. Thanks.
Jeff wrote to Gluon <=-
For what it's worth, a while back I set up Mystic on a Pi Zero W to see how it would perform. It did well, so a few days ago I moved my
(currently under development) BBS to it. All of the files in the Mystic home directory are on the SD card, but all of the Mystic subdirectories are links to a network drive. So far, so good.
Admittedly, it hasn't been load-tested with actual users but with
respect to message processing, I did request a full %RESCAN for all
fsxNet message bases. It took a couple of hours to process that many messages, but it did not crash. The BBS was a little slower than usual during the message processing, but was still usable by at least one
user (me).
That's something I might need to consider if there's too much I/O on the SD card. I was also considering the possibility of limiting the amount
of messages that fidopoll gets from the hub when you run it, but I
haven't seen any options for that. Right now I'm in the process of
waiting for my fsxNet address, so I can't test it yet. I wonder how many messages it'll poll the first time I run it and whether that can
overwhelm my Pi 3.
Jeff wrote to Gluon <=-
I doubt it. I had the %RESCAN set for 999 days, so there were a LOT of messages. If a Pi Zero W can handle them with only breaking a little sweat, a Pi 3 should do just fine. The Pi Zero W has half the memory (512GB) and only one core instead of 4.
Yeah, makes sense. Where can I set that %RESCAN parameter? Is it some option inside Mystic's configuration console?
On 05-22-20 15:10, Gluon wrote to Vk3jed <=-
Really? Why? Compressing from *.pkt to arcmail bundles causes a fair
bit of I/O.
I was thinking that most of the compression was happening in RAM and
then only one file would be output to the SD, but yeah, at least input
for every file still happens.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 90 |
Nodes: | 16 (0 / 16) |
Uptime: | 08:16:44 |
Calls: | 5,073 |
Calls today: | 5 |
Files: | 8,491 |
Messages: | 352,800 |