• SM_SYSSTAT

    From Hax0r@VERT to All on Tue Aug 8 11:46:00 2000
    Ok, if I excute the following in a baja module, i as the sysop should be kept track of in the log etc -- correct?

    or _sys_mic _SM_SYSSTAT

    correct?

    ---
    Synchronet hax0r's palace - unknown-realm.dynip.com - you've been hax0r'd
  • From Digital Man@VERT to Hax0r on Thu Aug 10 02:43:22 2000
    RE: SM_SYSSTAT
    BY: Hax0r to All on Tue Aug 08 2000 06:46 pm

    Ok, if I excute the following in a baja module, i as the sysop should be kep track of in the log etc -- correct?

    Which log? If you're talking about the detailed log, all remote (including telnet sessions are logged this way).

    or _sys_mic _SM_SYSSTAT

    correct?

    This will include the sysop's activity in the system statistics and the sysop's login/offs in the "last few callers" list.

    But why do it via Baja? This same option is togglable in SCFG.

    Rob
    ---
    Synchronet Vertrauen Home of Synchronet telnet://vert.synchro.net
  • From Hax0r@VERT to Digital Man on Thu Aug 10 15:19:00 2000
    RE: SM_SYSSTAT
    BY: Digital Man to Hax0r on Thu Aug 10 2000 09:43 am

    or _sys_mic _SM_SYSSTAT

    correct?

    This will include the sysop's activity in the system statistics and the syso login/offs in the "last few callers" list.

    But why do it via Baja? This same option is togglable in SCFG.

    The reason I am doing it this way is because the SCFG setting doesnt not differentiate amongst users with access level greater than 90. I have a user with access level 90 on my board (besides myself) and I would like them included in the daily callers and system logon/off stats, but not myself. Basically, I was going to have a compare statement in my LOGON module to check to see if the user# of the person logged in is <> to 1..... if this was the case, then or _sys_misc _SM_SYSSTAT. At first, I thought that my compare was hosed up -- so I just tried that line by itself, but it still did not include me in the LFC and logon stats.

    Heh -- whats up with it?

    ---
    Synchronet hax0r's palace - unknown-realm.dynip.com - you've been hax0r'd
  • From Digital Man@VERT to Hax0r on Fri Aug 11 04:51:49 2000
    RE: SM_SYSSTAT
    BY: Hax0r to Digital Man on Thu Aug 10 2000 10:19 pm

    or _sys_mic _SM_SYSSTAT

    correct?

    This will include the sysop's activity in the system statistics and the s login/offs in the "last few callers" list.

    But why do it via Baja? This same option is togglable in SCFG.

    The reason I am doing it this way is because the SCFG setting doesnt not differentiate amongst users with access level greater than 90. I have a use with access level 90 on my board (besides myself) and I would like them included in the daily callers and system logon/off stats, but not myself. Basically, I was going to have a compare statement in my LOGON module to che to see if the user# of the person logged in is <> to 1..... if this was the case, then or _sys_misc _SM_SYSSTAT. At first, I thought that my compare wa hosed up -- so I just tried that line by itself, but it still did not includ me in the LFC and logon stats.

    Heh -- whats up with it?

    Sounds like you're not doing it soon enough in the login sequence.

    Rob
    ---
    Synchronet Vertrauen Home of Synchronet telnet://vert.synchro.net
  • From PistolGrip@VERT to Hax0r on Fri Aug 11 08:53:00 2000
    RE: SM_SYSSTAT
    BY: Digital Man to Hax0r on Fri Aug 11 2000 11:51 am

    Sounds like you're not doing it soon enough in the login sequence.

    You might try it in the LOGIN module instead of LOGON.

    PistolGrip


    ---
    Synchronet WasteLand BBS telnet://wasteland.darktech.org
  • From Hax0r@VERT to Digital Man on Fri Aug 11 13:05:00 2000
    RE: SM_SYSSTAT
    BY: Digital Man to Hax0r on Fri Aug 11 2000 11:51 am

    or _sys_mic _SM_SYSSTAT

    correct?
    Sounds like you're not doing it soon enough in the login sequence.

    Well, I had it in the LOGON.SRC file, originally at the top (as one of the first lines) and then in the bottom -- how much "sooner" can i get :)

    Well, I tried it as the *very* first line of code in LOGIN.SRC (after the include of SBBS.DEFs.... and it STILL did not do what it was supposed to -- whats up with that?

    ---
    Synchronet hax0r's palace - unknown-realm.dynip.com - you've been hax0r'd
  • From PistolGrip@VERT to Hax0r on Fri Aug 11 15:21:00 2000
    RE: SM_SYSSTAT
    BY: Hax0r to Digital Man on Fri Aug 11 2000 08:05 pm

    Well, I tried it as the *very* first line of code in LOGIN.SRC (after the include of SBBS.DEFs.... and it STILL did not do what it was supposed to -- whats up with that?

    I know it's stupid, but can you post the line(s) of code you are using to try and do this?

    PistolGrip


    ---
    Synchronet WasteLand BBS telnet://wasteland.darktech.org
  • From Hax0r@VERT to PistolGrip on Sat Aug 12 19:52:00 2000
    RE: SM_SYSSTAT
    BY: PistolGrip to Hax0r on Fri Aug 11 2000 10:21 pm

    I know it's stupid, but can you post the line(s) of code you are using to tr and do this?

    # LOGIN.SRC
    !include sbbsdefs.inc
    or _sys_misc SM_SYSSTAT


    **rest of LOGIN Process here

    Which incidentally *will* include everyone EXCEPT #1 in the stats w/ LVL>90. I'm not sure if this is by design, but is definately cool if you code baja and tend to logon/off alot.

    I originally thought that it was not working as it should, but it turns out that I was testing it with user account #1 lvl 99, and was not showing up in the lfc and daily callers logs..... however user account #3 w/ Lvl 95 shows up consistently with that line in there.

    ---
    Synchronet hax0r's palace - unknown-realm.dynip.com - you've been hax0r'd