Modified Files:
modopts.ini
Log Message:
[logon] section: removed last_few_callers (moved to [logonlist]) and added show_logon_list
Added [logonlist] section, see http://wiki.synchro.net/module:logonlist for details.
Re: ctrl/modopts.ini
By: rswindell to CVS commit on Sun Mar 29 2020 07:59 pm
Modified Files:
modopts.ini
Log Message:
[logon] section: removed last_few_callers (moved to [logonlist]) and added show_logon_list
Added [logonlist] section, see http://wiki.synchro.net/module:logonlist for details.
I had a look at that page on the wiki and got logonlist set up. One thing I noticed is that the wiki page says to set up maintenance (?logonlist -m) in both the Daily Event and a "System Timed Event".
Does it need to only be run once daily?
When I run ?logonlist -l, it says I'm the first caller of
the day, even though my BBS has had callers. When I run ?logonlist -y, it displays yesterday's callers as expected.
I have ?logonlist -m set up as the Daily Event, but I was wondering if it needs to be run periodically as a System Timed Event?
But even after
running ?logonlist -m now, when I use the -l option, it still says I'm the first caller of the day and it doesn't display the day's callers.
I had a look at that page on the wiki and got logonlist set up. One
thing I noticed is that the wiki page says to set up maintenance
(?logonlist -m) in both the Daily Event and a "System Timed Event".
Ah, thanks, typo on my part. "logonlist install" does do the right thing though and adds "?logonlist -m" as the system's daily event.
Does it need to only be run once daily?
Yes.
But even after
running ?logonlist -m now, when I use the -l option, it still says I'm
the first caller of the day and it doesn't display the day's callers.
Right, I'm guessing because you rolled-over the data/logon.jsonl file (to logon.0.jsonl) prematurely. So long as the maintenace runs close to midnight, which it will as a daily event, it'll work as expected.
Ah, thanks, typo on my part. "logonlist install" does do the right thing though and adds "?logonlist -m" as the system's daily event.
Re: ctrl/modopts.ini
By: Digital Man to Nightfox on Sun Mar 29 2020 09:33 pm
Ah, thanks, typo on my part. "logonlist install" does do the right thing though and adds "?logonlist -m" as the system's daily event.
I'm curious why the Daily Event option was added?
I'd think the logonlist
maintenance could be set up as a Timed Event to run at (or near) midnight every day.
Also, since the Daily Event is configurable, I'd think that
could be configured to run something else other than the logonlist maintenance..
I'm curious why the Daily Event option was added?
It's actually always been there.
I'd think the logonlist
maintenance could be set up as a Timed Event to run at (or near)
midnight every day.
I suppose, but then it'd have to run in the event thread, which is optional (can be disabled) and can also be delayed while other timed events are running. The System Daily Event cannot be disabled and runs in the node's thread (the first node thread to be created in a new day) if the event thread isn't running. So it's more dependable than a timed event. You could try it as a timed event and let me know how it works out?
Also, since the Daily Event is configurable, I'd think that
could be configured to run something else other than the logonlist
maintenance..
Yeah, but I don't think anybody is/was using it for anything. Ideally, the sytem daily event would be a list of events to run instead of just a single. I used to use a batch file that did a bunch of things, but those have been replaced with timed events.
I still have a batch file that runs all of my daily maintenance stuff. I thought it would be simpler to have my daily maintenance as one (timed) event rather than making it a bunch of different events.
I still have a batch file that runs all of my daily maintenance stuff.
I thought it would be simpler to have my daily maintenance as one
(timed) event rather than making it a bunch of different events.
Yup, that's still a practical solution. Batch files are of course, platform (Windows) specific, and Synchronet being cross-platform and Vertrauen being a multi-platform system, I try to avoid using platform-specific solutions as much as possible.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 376 |
Nodes: | 16 (2 / 14) |
Uptime: | 69:25:56 |
Calls: | 8,042 |
Calls today: | 1 |
Files: | 13,040 |
Messages: | 5,833,295 |