I initially (over a year ago) had Mystic running on Pi, with SMB (and also tried NFS) shares to my NAS for messages and files, nogo - didn't like that
at all. I guess there's direct writes going on?

Has anyone tried this recently? Has this been fixed yet?

Cheers!
J

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
* Origin: The Gatehouse BBS (bbs.digitaglatehouse.com) (21:1/159)

I initially (over a year ago) had Mystic running on Pi, with SMB (and
also tried NFS) shares to my NAS for messages and files, nogo - didn't like that at all. I guess there's direct writes going on?

How are you attempting to use it? I am assuming you mounted the NFS share to a local directory and configured Mystic to point to the local mounted directory?

I think that would be the proper approach in Unix. In Windows you could probably use the \\naming convention to access it directly or mount it as a drive as well.

--- Mystic BBS v1.12 A39 2018/01/06 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

How are you attempting to use it? I am assuming you mounted the NFS

I've tried both NFS and SMB shares for msgs and files - Nada for both.
I'm running Ubuntu linux with QNAP NAS advertising both shares.

Access/security a non issue, I send backups to the exact same share (through either NFS or SMB) through a cron job.

Thanks

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
* Origin: The Gatehouse BBS (bbs.digitaglatehouse.com) (21:1/159)

How are you attempting to use it? I am assuming you mounted the NFS

I've tried both NFS and SMB shares for msgs and files - Nada for both.
I'm running Ubuntu linux with QNAP NAS advertising both shares.

The reason I am asking how you're mounting the NFS is because direct IO to a NFS mounted directory should work -- Thats exactly what NFS is designed to do, otherwise every program out there would need to be rewritten specifically to support NFS.

If you're trying to use a notation like nfs://server/path/ in Mystic it will not work. But if you're mounting it to say "/mysharedfiles/" and you configure a file base to look for files there, it should work.

Mystic won't mount your NFS and access to NFS is per-user, so your BBS user would both need access and must be provided with a fully mounted local directory at startup.

I don't have an NFS to test with, so I want to cover the basics first just to make sure we're on the same page before I try to figure out what the next
steps are.

EDIT: I just did a quick Google and what I am saying here is reinforced by a RedHat bugfix where direct I/O wasn't working properly with NFS:

https://bugzilla.redhat.com/show_bug.cgi?id=647297

--- Mystic BBS v1.12 A39 2018/01/08 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

The reason I am asking how you're mounting the NFS is because direct IO
to a NFS mounted directory should work -- Thats exactly what NFS is

I'm using etc/fstab for the NFS mount. On the host side, I have guest access read/write (currently for troubleshooting). here's my mount:

X.X.X.X:/BBS /mnt/BBS nfs rsize=8192,wsize=8192,timeo=14,intr,noauto,x-systemd.automount 0 0

But I guess you've answered the first question in that CIFS/SMB shares won't work, and it must be NFS for direct I/O.

Thanks!
j

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: The Gatehouse BBS (bbs.digitaglatehouse.com) (21:1/159)

But I guess you've answered the first question in that CIFS/SMB shares won't work, and it must be NFS for direct I/O.

I am not saying it won't work, I just didn't talk specifically about Samba because I haven't worked with it in Unix. I guess my official answer is "I don't know". :)

I believe you should be able to mount it in the same way you do with NFS but it may only work for file searches, not reading and writing. What I do know is that I would like it to work if it doesn't.

Maybe tomorrow I will have some time and I can try to set up Samba between my Windows 10 deskstop and Ubuntu laptop. I've been meaning to try to do the same between an OS/2 VMWare and Windows as well, so maybe I can try both.

The truth is though I have too many goals to try to complete tomorrow (which is usually my big programming day) so I don't know if I'll get to it or not.

--- Mystic BBS v1.12 A39 2018/01/08 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 01/12/18, g00r00 said the following...

I believe you should be able to mount it in the same way you do with NFS but it may only work for file searches, not reading and writing. What I do know is that I would like it to work if it doesn't.

You should be able to r/w over smb like any local filesystem as long as the share is mounted and you have appropriate permissions. The vfs driver should
be handling the dirty work.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

The truth is though I have too many goals to try to complete tomorrow (which is usually my big programming day) so I don't know if I'll get to

No worries. If I can help in any way (testing etc.) please let me know.

Thanks!
J

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: The Gatehouse BBS (bbs.digitaglatehouse.com) (21:1/159)

I believe you should be able to mount it in the same way you do with but it may only work for file searches, not reading and writing. Wha do know is that I would like it to work if it doesn't.

You should be able to r/w over smb like any local filesystem as long as the share is mounted and you have appropriate permissions. The vfs
driver should be handling the dirty work.

This was my assumption as well (although I haven't tried it in Unix). These protocols wouldn't be successful if they required every application to be rewritten specifically to support them.

--- Mystic BBS v1.12 A39 2018/01/15 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)