Good afternoon,
I had a chance today to recreate the issue I was having last weekend. I
copied all of the contents of my /sbbs/fido directory to /sbbs/u/fido,
which is on an nfs share. I then renamed /sbbs/fido to /sbbs/fido.old, and created a symlink to /sbbs/u/fido in the /sbbs directory as /sbbs/fido.

I have the same issue if I change the sbbsecho.ini to point to /sbbs/u/fido rather than attempt to use a symlink (the symlink is non-existant in that
test case).

Here is what sbbsecho did when attempting to process inbound mail:

Scanning for Inbound Packets...
Scanning secure inbound: /sbbs/fido/inbound/
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ inbound/0005B525.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ inbound/0005B53B.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ inbound/0005B550.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ inbound/0005B563.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ inbound/0005B573.PKT
Unpacking bundle: /sbbs/fido/inbound/0000FF5B.MO2 (9.3KB)
Executing: unzip -ojC /sbbs/fido/inbound/0000FF5B.MO2 -d /sbbs/fido/inbound/ Archive: /sbbs/fido/inbound/0000FF5B.MO2
inflating: /sbbs/fido/inbound/0005C1D0.PKT
Deleting /sbbs/fido/inbound/0000FF5B.MO2 (from line 2740)
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ inbound/0005B525.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ inbound/0005B53B.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ inbound/0005B550.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ inbound/0005B563.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ inbound/0005B573.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ inbound/0005C1D0.PKT
Scanning non-secure inbound: /sbbs/fido/in/
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ in/0005B525.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ in/0005B53B.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ in/0005B550.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ in/0005B563.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ in/0005B573.PKT
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ in/0005C1D0.PKT

Those are all the errors that I receive.

It then goes on to scan for inbound netmail and then exits with a 0, even though it never was able to toss any of the PKT files listed above. If I remove the ~fido symlink and restore the /sbbs/fido directory, these PKT
files are tossed as normal, no ERROR 11 messages and no exiting with 0
even though it failed.

I have the same issue if I change the sbbsecho.ini to point to /sbbs/u/fido rather than attempt to use a symlink.

Both systems are running Debian 9, and I am otherwise able to read and
write to the nfs share from the system running sbbs. The sbbsecho source says it is v 3.117 2019/06/29

Thanks!

---
þ SLMR 2.1a þ Never judge a man by his taglines.
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: ERROR 11 with sbbsecho
By: Dumas Walker to DIGITAL MAN on Sun Oct 20 2019 04:20 pm

Good afternoon,
I had a chance today to recreate the issue I was having last weekend. I copied all of the contents of my /sbbs/fido directory to /sbbs/u/fido,
which is on an nfs share. I then renamed /sbbs/fido to /sbbs/fido.old, and created a symlink to /sbbs/u/fido in the /sbbs directory as /sbbs/fido.

I have the same issue if I change the sbbsecho.ini to point to /sbbs/u/fido rather than attempt to use a symlink (the symlink is non-existant in that test case).

Here is what sbbsecho did when attempting to process inbound mail:

Scanning for Inbound Packets...
Scanning secure inbound: /sbbs/fido/inbound/
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ inbound/0005B525.PKT

It seems like the NFS share doesn't want to let you open the file.

Those are all the errors that I receive.

It then goes on to scan for inbound netmail and then exits with a 0, even though it never was able to toss any of the PKT files listed above. If I remove the ~fido symlink and restore the /sbbs/fido directory, these PKT files are tossed as normal, no ERROR 11 messages and no exiting with 0
even though it failed.

I have the same issue if I change the sbbsecho.ini to point to /sbbs/u/fido rather than attempt to use a symlink.

Both systems are running Debian 9, and I am otherwise able to read and
write to the nfs share from the system running sbbs. The sbbsecho source says it is v 3.117 2019/06/29

That's not the latest revision, but I don't expect the current code to behave any differently.

You could experiment with the code (sbbsecho.c, nopen.c) if you like, but I don't have any concrete suggestions.

digital man

Synchronet "Real Fact" #70:
Rob Swindell was interviewed for Jason Scott's BBS Documentary in July of 2002. Norco, CA WX: 73.8øF, 23.0% humidity, 0 mph W wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Scanning for Inbound Packets...
Scanning secure inbound: /sbbs/fido/inbound/
ERROR 11 (Resource temporarily unavailable) line 5619 opening /sbbs/fido/ inbound/0005B525.PKT

It seems like the NFS share doesn't want to let you open the file.

I figured that but was not sure why, since I am able to open them
otherwise. Matter of fact, it is doing so as I type this message. :)

You could experiment with the code (sbbsecho.c, nopen.c) if you like, but I don
t have any concrete suggestions.

I may need to figure out a different solution to what I am working on.
Thanks!

---
þ SLMR 2.1a þ ETHERNET - A device for catching the ether bunny.
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: ERROR 11 with sbbsecho
By: Dumas Walker to DIGITAL MAN on Mon Oct 21 2019 12:56 pm

It seems like the NFS share doesn't want to let you open the file.

I figured that but was not sure why, since I am able to open them otherwise. Matter of fact, it is doing so as I type this message. :)

Keep in mind, that your SBBS processes may be running under a different user - and your NFS permissions may not allow that user to access the files on the share. I guess this is particularly true if SBBS is running as root... (which nfs will change to "nobody" unless you have no_root_squash in your exports.
...ëîå*

... A truly wise man never plays leapfrog with a unicorn.

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!

Keep in mind, that your SBBS processes may be running under a different user - >nd your NFS permissions may not allow that user to access the files on the shar
. I guess this is particularly true if SBBS is running as root... (which nfs wi
l change to "nobody" unless you have no_root_squash in your exports.

I thought about that, but the issue shows itself even when it is being run outside of sbbs, i.e. if I run sbbsecho from the command line I still get
the same errors.

---
þ SLMR 2.1a þ OPCODE: MWAG = Make Wild-Assed Guess
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

I thought about that, but the issue shows itself even when it is being run outside of sbbs, i.e. if I run sbbsecho from the command line I still get
the same errors.

---
­ SLMR 2.1a ­ OPCODE: MWAG = Make Wild-Assed Guess
­ Synchronet ­ CAPCITY2 * capcity2.synchro.net *
Telnet/SSH:2022/Rlogin/HTTP

it still runs as a bbs user that is set in sbbs.ini

---
­ Synchronet ­ Richard's Fun House BBS | http://richardf.ddns.net

Re: ERROR 11 with sbbsecho
By: Dumas Walker to ALTEREGO on Tue Oct 22 2019 06:43 pm

I thought about that, but the issue shows itself even when it is being run outside of sbbs, i.e. if I run sbbsecho from the command line I still get
the same errors.

Right, and if you run it as root, and NFS is configure to drop root to "nobody" you'll get those errors.

What do you run it as? Does "id" of the user you run it as show a uid > 0? ...ëîå*

... A pnp transistor will be an npn.

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!

I thought about that, but the issue shows itself even when it is being run outside of sbbs, i.e. if I run sbbsecho from the command line I still get the same errors.

it still runs as a bbs user that is set in sbbs.ini

That should be the same user that otherwise has access to the share. FYI,
the /dirs directory is also mapped to the same nfs share and I have no
issues with it being there.

---
þ SLMR 2.1a þ If you believe in telekinesis, please raise my hand.
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

I thought about that, but the issue shows itself even when it is being run >outside of sbbs, i.e. if I run sbbsecho from the command line I still get
the same errors.

Right, and if you run it as root, and NFS is configure to drop root to "nobody
you'll get those errors.

What do you run it as? Does "id" of the user you run it as show a uid > 0?

When I am running outside of sbbs, it runs as an uid > 1000. It is also
the same share the /dirs directory is on, and sbbs accesses it fine.

---
þ SLMR 2.1a þ  Lifting Shadows Off a Dream
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP