I'd posted awhile back saying that one of my File Conferences, which lives on a









































































































































































































































































































































































































































































































































































































































































































































































































NAS drive connected to my BBS box, had bad permissions and wouldn't let users download files.

Well, thats not exactly right. I ssh into my BBS box [system], and simply type 'cp /mnt/Backup4TB/ROMs/rom/SegaMasterDrive/'Zool 64 [!].sms' .'... (or any file) and my 'pi' user has no problem copying files from that mounted drive...

When users, or me since I'be blocked the conference, goto that File Conference... add files to batch, or whatever, and download - they get:

Sending ZRINIT
Warning: recv_raw: Cancelled remotely
Warning: recv_init: Receive ZCAN instead of ZFILE or ZFIN
Hit any key or wait 60 seconds to continue...

So... I don't think its permissions. As stated, its a NAS NFS drive that I mount with a script every hour, just to make sure its there for 'users'... files are there, in /mnt/Backup4TB/* and I *think* I have Mystic setup correctly. I FIRST added them as CD-Rom drives so Mystic would copy the files over first - but then changed that to normal... any suggestions or; I have 4TB of ROMs *in* File Areas ready to serve to BBS users and ... can't. Grrr.

Thanks, in case anyone reads some issue that I haven't seen yet.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/05/03 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)

On 31 May 2021, paulie420 said the following...

I'd posted awhile back saying that one of my File Conferences, which
lives on a NAS drive connected to my BBS box, had bad permissions and

Well, thats not exactly right. I ssh into my BBS box [system], and
simply type 'cp /mnt/Backup4TB/ROMs/rom/SegaMasterDrive/'Zool 64
[!].sms' .'... (or any file) and my 'pi' user has no problem copying
files from that mounted drive...
Thanks, in case anyone reads some issue that I haven't seen yet.

Paulie can you post that line from your /etc/fstab and also the applicable lines from /etc/export ?

I'll be happy to take a look at it and see if anything pops out at me :)

And I've never installed Mystic on a Pi, so I'll need to ask you what user is Mystic running under?

Also, you may want to create a symlink to that NFS mountpoint somewhere in
your mystic directory tree just so everything is kinda where you would expect it to be in Mystic.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: V'Ger - Vger.Cloud (1337:3/116)

Thanks, tallship, for trying to help...

Paulie can you post that line from your /etc/fstab and also the
applicable lines from /etc/export ?

So currently I've just been running a .sh script, something like:
$ ~/mystic/mountroms.sh
#!/bin/bash

sudo mount -t nfs 10.0.0.13:/export/Backup4TB /mnt/Backup4TB

...I currently have my fstab entry commented out, I don't remember exactly why... heres my /etc/fstab anyway:

pi@bbs:~ $ cat /etc/fstab
proc /proc proc defaults 0 0 PARTUUID=fad0b673-01 /boot vfat defaults 0 2 PARTUUID=fad0b673-02 / ext4 defaults,noatime 0 1
# a swapfile is not a swap partition, no line here
# use dphys-swapfile swap[on|off] for that
#10.0.0.16:/export/Backup4TB /var/Backup4TB nfs defaults 0 0

And it seems like I don't have an /etc/export. What is that??? I know a lot with Linux, but... I'm reminded often that the 'lot' that I know is little to others. :P

Anyway, if I remember correctly I was mounting the NFS in my /etc/fstab but then commented it out for a bit as I tested; somehow switched to this script, but... the drive is there, unless the way I'm doing it is fubar. :P



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/05/03 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)

On 01 Jun 2021, paulie420 said the following...

Thanks, tallship, for trying to help...

Paulie can you post that line from your /etc/fstab and also the applicable lines from /etc/export ?

So currently I've just been running a .sh script, something like:
$ ~/mystic/mountroms.sh
#!/bin/bash

sudo mount -t nfs 10.0.0.13:/export/Backup4TB /mnt/Backup4TB

...I currently have my fstab entry commented out, I don't remember exactlywhy... heres my /etc/fstab anyway:

pi@bbs:~ $ cat /etc/fstab
proc /proc proc defaults 0 0 PARTUUID=fad0b673-01 /boot vfat defaults 0 2 PARTUUID=fad0b673-02 / ext4 defaults,noatime 0 1 # a swapfile is not a swap partition, no line here
# use dphys-swapfile swap[on|off] for that #10.0.0.16:/export/Backup4TB /var/Backup4TB nfs defaults 0 0

And it seems like I don't have an /etc/export. What is that??? I know a lotwith Linux, but... I'm reminded often that the 'lot' that I know is little toothers. :P

Anyway, if I remember correctly I was mounting the NFS in my /etc/fstab butthen commented it out for a bit as I tested; somehow switched to this script,but... the drive is there, unless the way I'm doing it is fubar.
:P

your nfs /etc/export should be /etc/exports and that is found on the system that you're sharing the folders from in there you will have 1 line per share, showing something like;

# cat /etc/exports
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
/mnt/shared *(rw,sync,no_root_squash,subtree_check)


once you have set up your nfs shares in that file, save and quit and then run `exportfs -r` to enable (or refresh) any nfs shares you just setup the reason you may have disabled the mounting in fstab is when rebooting the nfs client, ie your bbs pi, if the mount/networking is unavailable at the time it's booting








































































































































































































































































































































































































































































































































































































































































































































































































it will hang the boot.

I would prolly say using the script after it's booted to mount is better unless








































































































































































































































































































































































































































































































































































































































































































































































































the nfs mount and the pi will always be available, then use fstab.


Hope this helps paulie420 =)

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

--- Mystic BBS v1.12 A47 2020/12/04 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (1337:1/101)

your nfs /etc/export should be /etc/exports and that is found on the system that you're sharing the folders from in there you will have 1
line per share, showing something like;

Thank you. Again, shows what I know and don't... :P Heres my /etc/exports on the NAS system:
paulie420@Matrix:/etc $ cat exports
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
/export/Backup4TB 10.0.0.0/24(fsid=1,rw,subtree_check,insecure) /export/Btrfs4TB 10.0.0.0/24(fsid=2,rw,subtree_check,insecure)

# NFSv4 - pseudo filesystem root
/export 10.0.0.0/24(ro,fsid=0,root_squash,no_subtree_check,hide)

-----

the reason you may have disabled the mounting in fstab is when
rebooting the nfs client, ie your bbs pi, if the mount/networking is unavailable at the time it's booting it will hang the boot.

Ding ding, winner... I think you're correct. And I just switched to running a script to mount it while logged in - but... even with the script, and not setup







































































































































































































































































































































































































































































































































































































































































































































































































to mount automatically - it should WORK, right?

Thats why I never dug in and made sure the auto-mount setup was complete... like... with my script, the drive, directory and files are THERE... I can copy them to /mystic... but still users can't download. I'll gladly setup the fstab (and /etc/exports) correctly - but... I think I have to overcome the first problem - I think. If fixing those issues will solve the end-user no-download issue I'll happily run and do that. :P

I would prolly say using the script after it's booted to mount is better unless the nfs mount and the pi will always be available, then use fstab. Hope this helps paulie420 =)

Thanks... thats what I thought - that even tho I'm not using fstab I have to figure out WHY users cant download 1st... it does help, mL - and you were right... I had the fstab side worked out but possibly needed to do the server side setup.

Anyway, still at the same point but your words were knowledge - thats the best thing sir.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/05/03 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)

On 02 Jun 2021, paulie420 said the following...

paulie420@Matrix:/etc $ cat exports
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

# /etc/exports: the access control list for filesystems which may be exported# to NFS clients. See exports(5).
/export/Backup4TB 10.0.0.0/24(fsid=1,rw,subtree_check,insecure) /export/Btrfs4TB 10.0.0.0/24(fsid=2,rw,subtree_check,insecure)

# NFSv4 - pseudo filesystem root
/export 10.0.0.0/24(ro,fsid=0,root_squash,no_subtree_check,hide)

It "looks" ok, I assume that /export/Backup4TB is a valid and existing directory on the server that is sharing the files?

You might also want to look for file/directory ownership and permissions, as even though the shared filesystem is on another system, the user that is reading/writing from/to it needs to have access, so check that the UID/GUI of the "pi" user (I assume that's the user that will be reading/writing on the bbs/pi, make sure that what UID/GID it has on the bbs system, is also a valid UID/GID on the system that is sharing the files.

Make sure also that this UID/GID has access on the directory and files within for reading/writing.

Hope this helps.

the reason you may have disabled the mounting in fstab is when rebooting the nfs client, ie your bbs pi, if the mount/networking is unavailable at the time it's booting it will hang the boot.

Ding ding, winner... I think you're correct. And I just switched to running ascript to mount it while logged in - but... even with the
script, and not setupto mount automatically - it should WORK, right?

Yes, the script should work as long as you have the file sharing set up correctly. I used to always mount manually because it would always hang my system if the network share wasn't readable for some reason, but I have since ironed out those issues I had and now use fstab, but mounting it manually is the same as using fstab, so make sure it works manually first and it will then work in fstab.

Thanks... thats what I thought - that even tho I'm not using fstab I
have tofigure out WHY users cant download 1st... it does help, mL - and you wereright... I had the fstab side worked out but possibly needed to
do the serverside setup.

The best way to learn is to do what you did, ask questions, poke at the answer,







































































































































































































































































































































































































































































































































































































































































































































































































ask more questions, until it makes sense. Feel free to ask more =)

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

--- Mystic BBS v1.12 A47 2020/12/04 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (1337:1/101)

You might also want to look for file/directory ownership and
permissions, as even though the shared filesystem is on another system, the user that is reading/writing from/to it needs to have access, so
check that the UID/GUI of the "pi" user (I assume that's the user that will be reading/writing on the bbs/pi, make sure that what UID/GID it
has on the bbs system, is also a valid UID/GID on the system that is sharing the files.

Make sure also that this UID/GID has access on the directory and files within for reading/writing.

Hope this helps.

Ok, so I think this message will help me learn the proper setup no matter what... I had ASSUMED that...

I'm on user pi, sshed into my BBS box... and I just type:

cp /mnt/Backup4TB/foo/bar/file.zip .

And it copies... to user Pi's BBS box... so I thought that meant permissions were fine. But I HAVEN'T made sure UID,GID, etc is all setup perfect.

While I don't get how... user Pi can copy, but not thru Mystic... (Or, maybe ... the downloads are just failing...)

But I'm gonna dig thru your suggestions and see what I get out. THANK YOU mL.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/05/03 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)