• FIDOOUT Event

    From Max Haven@VERT/RDFIG to All on Mon Nov 17 07:15:00 2014
    How do I have the FIDOOUT event wait till a user logs off before it runs? Right now it runs after every post but I'd rather run it once when a user logs off the system.

    Thanks!


    ... I don't have any solution, but I certainly admire the problem.

    Max
    System Operator, Haven's Terminus
    --- SBBSecho 2.27-Linux
    * Origin: (
  • From Android8675@VERT/RDFIG/SHODAN to Max Haven on Mon Nov 17 11:41:00 2014
    By: Max Haven to All on Mon Nov 17 2014 06:03 am

    How do I have the FIDOOUT event wait till a user logs off before it runs? Right now it runs after every post but I'd rather run it once when a user logs off the system.

    I would call something to trigger the FIDOOUT event. http://wiki.synchro.net/config:semfiles - Semaphore files will force sbbs to trigger certain timed events, you just have to "touch" the file and sbbs will run the event.

    for Fidoout you'd want to:

    echo. > c:\sbbs\data\fidoout.now

    or in linux

    touch /sbbs/data/fidoout.now

    That'd force fidoout torun when a user logs out. By default Fidoout runs
    hourly on my board. I'm not sure if posting to an echo causes it to run as well, but there's probably a setting for that.

    Out of curiousity why do you want to wait to send fidonet stuff? these days messages can get to their destinations pretty quick, a user might even get a response to his message before he logs for the day.

    -a.
    ---
    ■ Synchronet ■ Shodan's Core - shodan.synchro.net:23 & :2323
  • From mark lewis@VERT/RDFIG to Android8675 on Mon Nov 17 21:16:00 2014
    On Mon, 17 Nov 2014, Android8675 wrote to Max Haven:

    How do I have the FIDOOUT event wait till a user logs off before
    it runs? Right now it runs after every post but I'd rather run it
    once when a user logs off the system.

    I would call something to trigger the FIDOOUT event.

    if i'm understanding max's post,the FIDOOUT event is already being triggered... it is being triggered each time a user saves a message...

    i'm suspecting thatshe is wanting to run the event only at logoff to give users the time to edit or delete posts they have written... it kinda sucks when

























































































































































































































































  • From Max Haven@VERT/RDFIG to mark lewis on Tue Nov 18 11:15:00 2014
    Re: FIDOOUT Event
    By: mark lewis to Android8675 on Mon Nov 17 2014 19:43:18

    How do I have the FIDOOUT event wait till a user logs off before
    it runs? Right now it runs after every post but I'd rather run it
    once when a user logs off the system.

    I would call something to trigger the FIDOOUT event.

    if i'm understanding max's post, the FIDOOUT event is already being triggered... it is being triggered each time a user saves a message...

    Yes! That is what is happening. I just wrote a message and 4 or 5 seconds after I saved it, Synchronet's log showed that it was running the FIDOOUT event.

    Nov 18 10:20:03 xxxx synchronet: term Node 1 Max posted on Fidonet Synchronet BBS Software Support
    Nov 18 10:20:07 xxxx synchronet: evnt Semaphore signaled for Timed Event: FIDOOUT
    Nov 18 10:20:07 xxxx synchronet: evnt Running native timed event: FIDOOUT
    Nov 18 10:20:13 xxxxsynchronet: evnt Timed event: FIDOOUT returned 0

    It looks like the semaphore was created when the message was saved. That's what I want to change. If I want to edit or delete a message I've just written, I can't because it has already been scanned out and sent. That's not good.

    i'm suspecting that she is wanting to run the event only at logoff to give users the time toedit or delete posts they have written... it kinda sucks when you go to edit or delete a post and find that it has alreadybeen scanned out and sent upstream...

    Exactly! ;)


    ... Open mouth, insert foot, echo internationally.

    Max
    System Operator, Haven's Terminus
    --- SBBSecho 2.27-Linux
    * Origin: (1:3634/50)