• ERROR 11 (Resource temporarily unavailable)

    From Dumas Walker@VERT/CAPCITY2 to Digital Man on Saturday, October 12, 2019 11:44:41
    I was trying to move my /sbbs/fido directory to an nfs share. sbbsecho does not seem to like this at all.

    I have a share, mounted as /sbbs/z. The bbs user has access to read, create, and delete files, and create and remove directories on this share (I verified this while having the issue).

    I copied everything out of /sbbs/fido into /sbbs/z/fido, and I changed my sbbsecho.ini settings as follows:

    inbound = /sbbs/fido/in/
    SecureInbound = /sbbs/fido/inbound/
    outbound = /sbbs/fido/out/

    to:

    inbound = /sbbs/z/fido/in/
    SecureInbound = /sbbs/z/fido/inbound/
    outbound = /sbbs/z/fido/out/

    I then removed /sbbs/fido and created a symlink, 'fido' in /sbbs that pointed to /sbbs/z/fido, just in case I forgot to change something.

    Both sbbsecho and binkit choked on this with ERROR 11 (Resource temporarily unavailable) messages. I tried changing the sbbsecho.ini back to :

    inbound = /sbbs/fido/in/
    SecureInbound = /sbbs/fido/inbound/
    outbound = /sbbs/fido/out/

    so that it would use the symlink. I tried sbbsecho again and it still barfed with the ERROR 11 messages.

    I tried this with synchronet not running just to make sure I was not getting any contention errors. I ran sbbsecho on a freshly booted machine, with only the environment set (as below) and no other instances of synchronet or sbbsecho running.

    export HOME=/sbbs
    export SBBSCTRL=/sbbs/ctrl
    export SBBSNODE=/sbbs/node1

    This did not fix the issue. I finally put everything back the way it was and sbbsecho is happy now.

    Is there some reason that sbbsecho only likes working with /sbbs/fido and only if it is not a symlink to elsewhere. or does not like nfs shares? I googled the ERROR 11 (Resource temporarily unavailable) message and the links that came up were all from developers who were asking questions on forums about fixing their code so that the messages would go away. I was not able to find anything that indicated how an enduser could make it go away.

    Thanks.

    ---
    Synchronet CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
  • From Richard Williamson@VERT/RICHARDF to Dumas Walker on Saturday, October 12, 2019 12:16:28
    what format is the nsf share?

    ---
    Synchronet Richard's Fun House BBS | http://richardf.ddns.net
  • From Rampage@VERT/SESTAR to Dumas Walker on Saturday, October 12, 2019 13:57:56
    Re: ERROR 11 (Resource temporarily unavailable)
    By: Dumas Walker to Digital Man on Sat Oct 12 2019 11:44:41

    Is there some reason that sbbsecho only likes working with /sbbs/fido and only if it is not a symlink to elsewhere.

    i cannot help with your problem but sbbsecho is not limited to using sbbs/fido... i changed mine to sbbs/ftn several months ago with i started working with 5D BSO... it is working fine once i figured out that sbbsecho will tack on the hex zone number to all outbound directories that are not the root outbound directory... it works fine and even binkd has no problems once we tell it a little white lie in each network's outbound directory definition :)


    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Rampage@VERT/SESTAR to Richard Williamson on Saturday, October 12, 2019 13:59:53
    Re: ERROR 11 (Resource temporarily unavailable)
    By: Richard Williamson to Dumas Walker on Sat Oct 12 2019 12:16:28


    what format is the nsf share?

    they can be any format... the OS and drivers hide all of that from the programs using them...


    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Tony Langdon@VERT to Rampage on Sunday, October 13, 2019 07:53:00
    On 10-12-19 13:57, Rampage wrote to Dumas Walker <=-

    Re: ERROR 11 (Resource temporarily unavailable)
    By: Dumas Walker to Digital Man on Sat Oct 12 2019 11:44:41

    Is there some reason that sbbsecho only likes working with /sbbs/fido and
    only if it is not a symlink to elsewhere.

    i cannot help with your problem but sbbsecho is not limited to using sbbs/fido... i changed mine to sbbs/ftn several months ago with i
    started working with 5D BSO... it is working fine once i figured out
    that sbbsecho will tack on the hex zone number to all outbound
    directories that are not the root outbound directory... it works fine
    and even binkd has no problems once we tell it a little white lie in
    each network's outbound directory definition :)

    I've never had issues with the outbound. Mine lives under /sbbs/binkd. And what little white lie did you tell binkd? ;) I run 5D BSO on my sbbsecho/binkd setup as well.


    ... Gee! How'd you ever get it to do THAT?
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Alterego@VERT/ALTERANT to Dumas Walker on Sunday, October 13, 2019 11:02:44
    Re: ERROR 11 (Resource temporarily unavailable)
    By: Dumas Walker to Digital Man on Sat Oct 12 2019 11:44 am

    Both sbbsecho and binkit choked on this with ERROR 11 (Resource temporarily unavailable) messages. I tried changing the sbbsecho.ini back to :

    At a (wild) guess, it might have something to do with file locking. But when DM responds, naturally, he'd probably have a good reason.

    (I remember in the past haveing issues with file locking over NFS - long time ago - cant remember if I resolved it - nfslockd comes to mind...)
    ...*

    ... It is impossible to please the whole world and your mother-in-law.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Rampage@VERT/SESTAR to Tony Langdon on Saturday, October 12, 2019 21:03:20
    Re: Re: ERROR 11 (Resource temporarily unavailable)
    By: Tony Langdon to Rampage on Sun Oct 13 2019 07:53:00

    i cannot help with your problem but sbbsecho is not limited to using
    sbbs/fido... i changed mine to sbbs/ftn several months ago with i
    started working with 5D BSO... it is working fine once i figured out
    that sbbsecho will tack on the hex zone number to all outbound
    directories that are not the root outbound directory... it works fine
    and even binkd has no problems once we tell it a little white lie in
    each network's outbound directory definition :)

    I've never had issues with the outbound. Mine lives under /sbbs/binkd.

    i went with sbbs/ftn because it covers all fidonet technology networks... it just seems to fit better than calling everything "fidonet"...

    And what little white lie did you tell binkd? ;)

    that the base zone for each of the nets is 1 for all of them instead of their actual zone number like true 5D BSO is normally set up with...

    I run 5D BSO on my sbbsecho/binkd setup as well.

    cool :) are you using my othernets list, too?


    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Tony Langdon@VERT to Rampage on Sunday, October 13, 2019 12:47:00
    On 10-12-19 21:03, Rampage wrote to Tony Langdon <=-

    i went with sbbs/ftn because it covers all fidonet technology
    networks... it just seems to fit better than calling everything "fidonet"...

    I went with /sbbs/binkd, based on past tradition, but could have put it anywhere. :)

    And what little white lie did you tell binkd? ;)

    that the base zone for each of the nets is 1 for all of them instead of their actual zone number like true 5D BSO is normally set up with...

    Oh, I did that too. Mystic also behaves in the same way.

    I run 5D BSO on my sbbsecho/binkd setup as well.

    cool :) are you using my othernets list, too?

    No, I should. Hvae to find it again (I'm sure you mentioned it a while back).


    ... I WAS PUT ON THIS EARTH TO MAKE YOUR LIFE MISERABLE.
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Dumas Walker@VERT/CAPCITY2 to RICHARD WILLIAMSON on Saturday, October 12, 2019 19:44:00
    what format is the nsf share?

    If you mean is it ext2, 3, or 4, it is ext3.

    ---
    SLMR 2.1a Do I straddle the fence on issues? Well, yes and no....
    Synchronet CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
  • From Dumas Walker@VERT/CAPCITY2 to RAMPAGE on Saturday, October 12, 2019 20:23:00
    i cannot help with your problem but sbbsecho is not limited to using sbbs/fido.
    . i changed mine to sbbs/ftn several months ago with i started working with 5D >SO... it is working fine once i figured out that sbbsecho will tack on the hex >one number to all outbound directories that are not the root outbound directory
    .. it works fine and even binkd has no problems once we tell it a little white >ie in each network's outbound directory definition :)

    Honestly, I think it is the nfs it does not like but I am not sure why. In past, I have occassionally run across software that does not like it.
    OTOH, my 'dirs' directory is on another nfs share and it has no issues with
    it.

    ---
    SLMR 2.1a Mistress: halfway between a mister and a mattress.
    Synchronet CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
  • From Dumas Walker@VERT/CAPCITY2 to ALTEREGO on Sunday, October 13, 2019 10:19:00
    Both sbbsecho and binkit choked on this with ERROR 11 (Resource temporarily
    unavailable) messages. I tried changing the sbbsecho.ini back to :

    At a (wild) guess, it might have something to do with file locking. But when DM
    responds, naturally, he'd probably have a good reason.

    You know, I seem to remember seeing another message that mentioned "file locking" so you may be onto something.

    (I remember in the past haveing issues with file locking over NFS - long time a
    o - cant remember if I resolved it - nfslockd comes to mind...)

    I will take a look into that package. Thanks!

    ---
    SLMR 2.1a Ensign Pillsbury? He's BREAD, Jim......
    Synchronet CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
  • From Dumas Walker@VERT/CAPCITY2 to Alterego on Monday, October 14, 2019 18:28:09
    Re: ERROR 11 (Resource temporarily unavailable)
    By: Alterego to Dumas Walker on Sun Oct 13 2019 11:02:44

    At a (wild) guess, it might have something to do with file locking. But when responds, naturally, he'd probably have a good reason.

    (I remember in the past haveing issues with file locking over NFS - long tim ago - cant remember if I resolved it - nfslockd comes to mind...)

    He actually has not responded as yet.

    I went looking for a package called nfslockd but did not find it in the debian respositories. there is a lockd that is included as a part of one of the nfs packages, though. I think that it, and statd, should be running on my server or I would be having many more issues than just with sbbsecho. I am going to investigate it some, though.

    ---
    Synchronet CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP