• Synchronet Inactivity timeout

    From Grease@1:229/2 to All on Sunday, November 24, 2019 10:26:44
    From: grease@DARKMATT.remove-2qf-this

    I've been doing different stuff to the bbs with menus and such. I was wondering
    if there is a way to extend the inactivity timeout? It seems like I get the "Are you really there?" after two minutes. It's fine for below 90 users, but I would like to
    extend it a bit for me.


    Grease
    darkmatt.synchro.net

    Grease

    ... Pohl's law: Nothing is so good that somebody, somewhere, will not hate it

    ---
    þ Synchronet þ Dark Matter BBS * darkmatt.synchro.net * Howdy from Texas!
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From MRO@1:229/2 to All on Sunday, November 24, 2019 13:06:23
    From: mro@BBSESINF.remove-9zw-this

    To: Grease
    Re: Synchronet Inactivity timeout
    By: Grease to All on Sun Nov 24 2019 10:26 am

    I've been doing different stuff to the bbs with menus and such. I was wonder if there is a way to extend the inactivity timeout? It seems like I get the "Are you really there?" after two minutes. It's fine for below 90 users, but would like to extend it a bit for me.


    yeah it's in scfg. take a look at the older documentation. there's a lot of stuff you can pick up.
    ---
    þ Synchronet þ ::: BBSES.info - free BBS services :::
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Grease@1:229/2 to All on Sunday, November 24, 2019 19:36:34
    From: grease@DARKMATT.remove-re2-this

    To: MRO
    Re: Synchronet Inactivity timeout
    By: MRO to Grease on Sun Nov 24 2019 01:06 pm

    yeah it's in scfg. take a look at the older documentation. there's a lot of stuff you can pick up.

    I'll take a look.

    Grease

    ... When people are free to do as they please, they usually imitate each other

    ---
    þ Synchronet þ Dark Matter BBS * darkmatt.synchro.net * Howdy from Texas!
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From HusTler@1:229/2 to All on Sunday, November 24, 2019 15:33:08
    From: hustler@HAVENS.remove-a2z-this

    To: Grease
    Re: Synchronet Inactivity timeout
    By: Grease to All on Sun Nov 24 2019 10:26 am

    I've been doing different stuff to the bbs with menus and such. I was
    wondering if
    there is a way to extend the inactivity timeout? It seems like I get the
    "Are you
    really there?" after two minutes. It's fine for below 90 users, but I
    would like to
    extend it a bit for me.

    Yes it's in SCFG/Nodes/Advanced

    Havens BBS

    SysOp: HusTler

    ---
    þ Synchronet þ Havens BBS havens.synchro.net
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Gamgee@1:229/2 to Grease on Sunday, November 24, 2019 19:47:00
    From: gamgee@PALANT.remove-jmn-this

    To: Grease
    Grease wrote to All <=-

    I've been doing different stuff to the bbs with menus and such. I
    was wondering if there is a way to extend the inactivity timeout?
    It seems like I get the "Are you really there?" after two
    minutes. It's fine for below 90 users, but I would like to extend
    it a bit for me.

    If you are the sysop, and properly registered yourself as User #1,
    you should have ALL exemptions and NO restrictions. One of the
    exemptions is the Inactivity timer.

    More here: http://wiki.synchro.net/access:exemptions



    ... Internal Error: The system has been taken over by sheep at line 19960
    --- MultiMail/Linux v0.52
    þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Grease@1:229/2 to All on Sunday, November 24, 2019 19:37:15
    From: grease@DARKMATT.remove-re2-this

    To: HusTler
    Re: Synchronet Inactivity timeout
    By: HusTler to Grease on Sun Nov 24 2019 03:33 pm

    Yes it's in SCFG/Nodes/Advanced

    The one section I didn't look in.

    Grease

    ... You keep saying that, I don't think it means what you think it means

    ---
    þ Synchronet þ Dark Matter BBS * darkmatt.synchro.net * Howdy from Texas!
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Digital Man@1:229/2 to All on Monday, November 25, 2019 12:16:12
    From: digital.man@vert.synchro.net.remove-olx-this

    To: Grease
    Re: Synchronet Inactivity timeout
    By: Grease to All on Sun Nov 24 2019 10:26 am

    I've been doing different stuff to the bbs with menus and such. I was wondering if there is a way to extend the inactivity timeout? It seems like I get the "Are you really there?" after two minutes. It's fine for below 90 users, but I would like to extend it a bit for me.

    Give yourself the 'H' exemption and you won't get it at all.

    digital man

    Synchronet/BBS Terminology Definition #24:
    DTE = Data Terminal Equipment
    Norco, CA WX: 66.5øF, 32.0% humidity, 1 mph ESE wind, 0.00 inches rain/24hrs --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Tony Langdon@1:229/2 to Grease on Monday, November 25, 2019 17:53:00
    From: tony.langdon@3:633/410.remove-x2c-this

    To: Gamgee
    On 11-24-19 19:47, Gamgee wrote to Grease <=-

    Grease wrote to All <=-

    I've been doing different stuff to the bbs with menus and such. I
    was wondering if there is a way to extend the inactivity timeout?
    It seems like I get the "Are you really there?" after two
    minutes. It's fine for below 90 users, but I would like to extend
    it a bit for me.

    If you are the sysop, and properly registered yourself as User #1,
    you should have ALL exemptions and NO restrictions. One of the
    exemptions is the Inactivity timer.

    I didn't have that by default. I had to tweak the inactivity timer settings for sysop users, from memory. :)


    ... Political Season: Does this mean we can shoot them?!?!
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Tony Langdon@1:229/2 to Grease on Monday, November 25, 2019 17:52:00
    From: tony.langdon@3:633/410.remove-x2c-this

    To: Grease
    On 11-24-19 10:26, Grease wrote to All <=-

    I've been doing different stuff to the bbs with menus and such. I was wondering if there is a way to extend the inactivity timeout? It seems like I get the "Are you really there?" after two minutes. It's fine for below 90 users, but I would like to extend it a bit for me.

    Yes, poke around in scfg. I've done the same for sysop level users. Ordinary users still have the 5 min timeout.


    ... Only those who attempt the absurd can achieve the impossible.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Dan Clough@1:229/2 to Tony Langdon on Tuesday, November 26, 2019 20:33:00
    From: dan.clough@1:123/115.remove-x2c-this

    To: Tony Langdon
    Tony Langdon wrote to Gamgee <=-

    I've been doing different stuff to the bbs with menus and such. I
    was wondering if there is a way to extend the inactivity timeout?
    It seems like I get the "Are you really there?" after two
    minutes. It's fine for below 90 users, but I would like to extend
    it a bit for me.

    If you are the sysop, and properly registered yourself as User #1,
    you should have ALL exemptions and NO restrictions. One of the
    exemptions is the Inactivity timer.

    I didn't have that by default. I had to tweak the inactivity
    timer settings for sysop users, from memory. :)

    If you are the first/actual/real Sysop, as User #1, you are by
    default configured with all exemptions and no restrictions.

    http://www.synchro.net/docs/system_config.html#CreatingSysopAccount

    If you are talking about designating subsequent user accounts as
    "sysops", then yes, you'd have to manually set their exemptions
    and restrictions.



    ... Don't wait for your ship to come in - swim out to it.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Gamgee@1:229/2 to Tony Langdon on Wednesday, November 27, 2019 07:35:00
    From: gamgee@PALANT.remove-yip-this

    To: Tony Langdon
    Tony Langdon wrote to Dan Clough <=-

    If you are the first/actual/real Sysop, as User #1, you are by
    default configured with all exemptions and no restrictions.

    How recent is that? I know it wasn't in 3.16. I can' recall if
    I had to tweak my second (start of 2018 at the time) 3.17
    installation.

    I'm not real sure. My first serious install was in late 2018, so
    was 3.17a or 3.17b, and it had it that way.

    Might be in a Changelog somewhere, but don't currently have the
    time to look... :-)



    ... Daddy, what does "now formatting drive C:" mean?
    --- MultiMail/Linux v0.52
    þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Digital Man@1:229/2 to All on Wednesday, November 27, 2019 08:50:33
    From: digital.man@vert.synchro.net.remove-uy6-this

    To: Tony Langdon
    Re: Re: Synchronet Inactivity timeout
    By: Tony Langdon to Dan Clough on Wed Nov 27 2019 07:11 pm

    On 11-26-19 20:33, Dan Clough wrote to Tony Langdon <=-

    If you are the first/actual/real Sysop, as User #1, you are by
    default configured with all exemptions and no restrictions.

    How recent is that? I know it wasn't in 3.16.

    Not a recent change. Definitely was there in v3.16. But if you created your user account using any method *other* than logging as "new" via the terminal server, then that would not be the case.

    digital man

    Synchronet "Real Fact" #43:
    Synchronet added Baja/PCMS support with v2.00a (1994).
    Norco, CA WX: 53.5øF, 66.0% humidity, 0 mph W wind, 0.00 inches rain/24hrs
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Tony Langdon@1:229/2 to Gamgee on Thursday, November 28, 2019 10:55:00
    From: tony.langdon@3:633/410.remove-mf8-this

    To: Gamgee
    On 11-27-19 07:35, Gamgee wrote to Tony Langdon <=-

    I'm not real sure. My first serious install was in late 2018, so
    was 3.17a or 3.17b, and it had it that way.

    Yeah I think I know what happened. I used a different account to the original sysop account in my first installation, so I had to manually tweak my account, even though it was given sysop level access.

    So this current installation probably didn't require me to tweak anything, because I am now using the original sysop account.


    ... Why do we say something is out of whack? What is a whack?
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Tony Langdon@1:229/2 to Dan Clough on Wednesday, November 27, 2019 19:11:00
    From: tony.langdon@3:633/410.remove-bgx-this

    To: Dan Clough
    On 11-26-19 20:33, Dan Clough wrote to Tony Langdon <=-

    If you are the first/actual/real Sysop, as User #1, you are by
    default configured with all exemptions and no restrictions.

    How recent is that? I know it wasn't in 3.16. I can' recall if I had to tweak my second (start of 2018 at the time) 3.17 installation.

    http://www.synchro.net/docs/system_config.html#CreatingSysopAccount

    If you are talking about designating subsequent user accounts as
    "sysops", then yes, you'd have to manually set their exemptions
    and restrictions.

    That stands to reason.



    ... Don't wait for your ship to come in - swim out to it.

    :)


    ... Old immortals don't die, they just... don't.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Tony Langdon@1:229/2 to Digital Man on Thursday, November 28, 2019 10:58:00
    From: tony.langdon@3:633/410.remove-mf8-this

    To: Digital Man
    On 11-27-19 08:50, Digital Man wrote to Tony Langdon <=-

    Not a recent change. Definitely was there in v3.16. But if you created your user account using any method *other* than logging as "new" via
    the terminal server, then that would not be the case.

    Yeah I've worked out what happened. It was because how the original incarnation of my system was setup. For some reason, I didn't use the original sysop account, but instead used a second account which had sysop access. Therefore I had to tweak the timeout settings for that account.

    So a case of "my bad". :D

    On the current system, I wouldn't have needed to tweak anything, because I am now using the original sysop account.


    ... Heresy is only another word for freedom of thought.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
    --- Synchronet 3.17c-Win32 NewsLink 1.111
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)