+ Feb 11 06:45:02 File fsxinfo.zip Area FSX_INFO From 21:1/100
! Feb 11 06:45:02 Bad filename; Moved to /media/usb1/bbs/files/badfile/ ! Feb 11 06:45:02 Failed moving file
! Feb 11 06:45:02 Failed moving TIC file
1. The file doesn't actually exist.
2. Access is not correct
3. You have your incoming directory on a different disk drive volume than your badfiles directory.
Ok may be part of the issue, I do have my badfiles directory in a different drive. On the Raspbery Pi I installed the main BBS softwrae on the SD card itself (/mystic) but my files and message bases are on a USB drive (/media/usb1/bbs)
Gotcha.
So this is a major issue with Mystic that I need to find a good way to address and it is at the very top of my list of things to do. Mystic in most places uses fast moving to quickly move a file, but it only works across the same volume.
I need to make an option to use "fast move" or "copy" which will be much slower and require much more disk interaction, but it will work across volumes. I'll probably make this an option in Mystic's General configuration and that setting will apply to all of Mystic and its utilities.
If you identify other areas where things seem to not copy let me know.
I know another one is if you rename your "filename" in a message base, Mystic will offer to rename the files for you but it won't when they are on a different volume.
On 02-12-19 12:29, g00r00 wrote to bamageek <=-
I need to make an option to use "fast move" or "copy" which will be
much slower and require much more disk interaction, but it will work across volumes. I'll probably make this an option in Mystic's General configuration and that setting will apply to all of Mystic and its utilities.
I think I ran into that one one time but I thought it was something I
did. Also, when I was configuring the echo nodes a couple of times some
of the settings didn't get saved the first time. For example, I
configured EchoMail nodes for fsxNet, then went to configure another network. When I went back to fsxNet, some of the settings were blank.
This happened a couple of times to me.
Most of my system paths are on the sd card under /mystic with the exception of Log FIle Path, Message Base Path, and File Attach Path
which are on the USB drive.
This is my third installation of mystic on this system. The first two times I installed everything on the USB drive, however, over time things seem to get corrupted, so this last time I bought a big SD card and installed the program and structure on the SD card.
I appreciate your help. I'm still learning. But this is a really great system!
It would be good to have this as an option as you're planning, because
for me, using the fast move would be preferable at this time, but the copy/delete option could be useful if I ever restructure my filesystems.
On 02-12-19 23:37, g00r00 wrote to Vk3jed <=-
What I've decided to try before I make it a configuration setting is
that it will always try a fast move, and if that fails then it will try
to do a traditional copy/delete. So it should always end up using the best method in all situations without a configuration change required, assuming that works :)
What I've decided to try before I make it a configuration setting is
that it will always try a fast move, and if that fails then it will try
to do a traditional copy/delete. So it should always end up using the best method in all situations without a configuration change required, assuming that works :)
Now I just need to find all of the places in Mystic where I need to add this.
However, "temp..." (eg: tempftn, tempmis, temputil) cannot be changed?
(or can they?), so they are /mystic/temp...
So when mutil runs, I suspect it creates a packet in temputil (/mystic/temputil) and tries to rename it to the outbound /mystic/data/echomail/out... but that silently fails because its another device.
So it it would be great to use copy/delete instead ...
I've had problems with both on my Pi and I think for me it was because
if power fluxuations by using a crap power supply, and also shutting the system down incorrectly by kicking the power cord out of the device. I had it powered by my desktop for a while and I would forget to shut the
Pi down first before my desktop so the Pi would aburptly get shutdown. Kills SD cards!
and loosing power intermitantly. Even aside from that if you look at
the pi wrong or just touch the power supply it seems to cause it to
drop. I need to see if I can rig up some kind of battery backup for this little guy.
I've got a 32 Gig SanDisk in it now so I'm hoping it will work better!
On 02-13-19 13:03, g00r00 wrote to deon <=-
If I were to change "/mystic/temp1" to something else then users will
be forced to go into their door configurations and use the door file
MCI code in their command lines. Most people I think hardcode their
door command lines to point to the temp directories instead of using
the MCI code. This is largely in part by my own tutorials doing it
that way :(
I've assumed part of my issue was I was just using recycled mobile
phone chargers as a power supply and not using one that was probably specced correctly for the Pi.
Even the PS that comes with the Pi "kit" doesn't work well :( I ended up getting a 50W USB Power bank and all my power problems went away
Symbolic links? :) That's what I normally use to get around things
which are hard coded or otherwise dependent.
On 14 Feb 2019, Vk3jed said the following...
Symbolic links? :) That's what I normally use to get around things which are hard coded or otherwise dependent.
Sure they fix the problem, but they are not a solution IMHO :)
Symbolic links? :) That's what I normally use to get around things which are hard coded or otherwise dependent.
Sure they fix the problem, but they are not a solution IMHO :)
On 02-14-19 13:19, deon wrote to Vk3jed <=-
On 14 Feb 2019, Vk3jed said the following...
Symbolic links? :) That's what I normally use to get around things
which are hard coded or otherwise dependent.
Sure they fix the problem, but they are not a solution IMHO :)
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 132:31:53 |
| Calls: | 2,073 |
| Files: | 11,136 |
| Messages: | 947,552 |