Subject: No log entries in sbbsctrl for ftp/qwk uploads?
@MSGID: <55D9D673.12069.dove.sync@realitycheckbbs.org>
@TZ: c1e0
I just upgraded everything to 3.17 from the pre-made builds and noticed that the Events window in sbbsctrl doesn't show results when you do an FTP upload of a QWK .REP packet.
Is this expected behavior?
Subject: No log entries in sbbsctrl for ftp/qwk uploads?
@MSGID: <55D9D673.12069.dove.sync@realitycheckbbs.org>
@TZ: c1e0
I just upgraded everything to 3.17 from the pre-made builds and noticed that the Events window in sbbsctrl doesn't show results when you do an FTP upload of a QWK .REP packet.
A lot of things are broken currently in the code in CVS (currently reported as v3.17a), especially for Windows, so I wouldn't recommend "upgrading" to it.
Do you mean your BBS uploading a DOVE-Net REP packet to vert or a user uploading a QWK .REP packet to your BBS?
Re: No log entries in sbbsctrl for ftp/qwk uploads?
By: Digital Man to Poindexter Fortran on Mon Aug 24 2015 04:50 pm
A lot of things are broken currently in the code in CVS (currently reported as v3.17a), especially for Windows, so I wouldn't recommend "upgrading" to it.
I have a backup of my 3.16 install. Would the bugs merit going back or might it be worth it to grin and bear it and do another CVS install in a while?
Re: No log entries in sbbsctrl for ftp/qwk uploads?
By: Deuce to Poindexter Fortran on Tue Aug 25 2015 12:03 am
Do you mean your BBS uploading a DOVE-Net REP packet to vert or a user uploading a QWK .REP packet to your BBS?
A user uploading a packet. I do most of my BBSing via QWK, and would watch the upload to see if I'd forgotten to delete a .REP packet.
I guess that's up to you. I'm currently only running v3.17 on *one* of my instances of Synchronet (the other 2 are still running v3.16) cause it's crashing pretty much daily right now. If you don't mind the crashes or missing features or are wanting to help detect and solve bugs, then please run the development code!
A lot of things are broken currently in the code in CVS (currently reported as v3.17a), especially for Windows, so I wouldn't recommend "upgrading" to it.
I have a backup of my 3.16 install. Would the bugs merit going back or might it be worth it to grin and bear it and do another CVS install in a while?
If you're happy reporting crashes and helping improve the next version, by all means, run 3.17. Be prepared to update regularly though since bugs are being found and fixed every day or two.
If you want something you can leave alone and expect to keep working without you putting extra effort in, use the latest release.
If you're happy reporting crashes and helping improve the next version, by all means, run 3.17. Be prepared to update regularly though since bugs are being found and fixed every day or two.
If you want something you can leave alone and expect to keep working without you putting extra effort in, use the latest release.
Deuce, I am also running the new 3.17 (on WinXP), and I think I can deal with some crashes and general buggy-ness. What can I do to help? How can I report crashes and such? What kind of info would you like?
On the plus side, I have seen crashes with 3.17 but the BBS is still chugging along and running until I acknowledge the crash and hit the "send" or "don't send" on the crash report. Once I touch one of those buttons, it all evaporates.
Deuce, I am also running the new 3.17 (on WinXP), and I think I can deal with some crashes and general buggy-ness. What can I do to help? How can I report crashes and such? What kind of info would you like?
On the plus side, I have seen crashes with 3.17 but the BBS is still chugging along and running until I acknowledge the crash and hit the "send" or "don't send" on the crash report. Once I touch one of those buttons, it all evaporates.
If it turns out that article isn't complete enough, we'll update it as needed. For Windows development builds, there may be Windows-specific things that can help out. Digital Man is the Windows guy, so I'll let him flesh it out if there's a way to get "good" info vs. "bad" info.
Re: Re: No log entries in sbbsctrl for ftp/qwk uploads?
By: Deuce to KenDB3 on Wed Aug 26 2015 03:16 am
If it turns out that article isn't complete enough, we'll update it as needed. For Windows development builds, there may be Windows-specific things that can help out. Digital Man is the Windows guy, so I'll let him flesh it out if there's a way to get "good" info vs. "bad" info.
Hi Deuce,
Is there a way to build the "stable" 3.16 version on Linux? I'm just following the install directions for Linux to build - I'm assuming this is a snapshot of current development code?
Is there a way to build the "stable" 3.16 version on Linux? I'm just following the install directions for Linux to build - I'm assuming this is a snapshot of current development code?
Deuce wrote to Poindexter Fortran <=-
If you want something you can leave alone and expect to keep working without you putting extra effort in, use the latest release.
Re: Re: No log entries in sbbsctrl for ftp/qwk uploads?
By: KenDB3 to Deuce on Tue Aug 25 2015 11:05 pm
If you're happy reporting crashes and helping improve the next
version, by all means, run 3.17. Be prepared to update regularly
Deuce, I am also running the new 3.17 (on WinXP), and I think I can
deal with some crashes and general buggy-ness. What can I do to help?
A debug stack trace would be the most helpful. Unfortunately, you need to use MSVC2013 to build the latest Synchronet for Windows and I don't think it'll run on WinXP. So if you have another Win7+ computer you can run MSVC on, you can download Visual Studio/C++ Express edition (12.0/2013) and build a debug version of the DLLs and run those with the sbbsctrl.exe from the sbbs-dev.zip. Then if it crashes, you should be able to capture a stack trace and provide it to us.
Speaking of regularly scheduled events... I run my backup from a batch file, it uses robocopy and 7zip, which works well. But when I tried to set it up as an event in SBBS, I tried to set it up to run the First Monday of every month. Which isn't really an option. So I tried to see if I could do some mutual exclusions based on the options available. Short story, it didn't work, but would it be possible to get something like this? Here is what I tried to do to see if it would only run the first Monday of the month:
Execution Months: Any
Execution Days of the Month: 1 2 3 4 5 6 7
Execution Days of the Week: Mon
So, instead of limiting it to just Monday the 1st or Monday the 2nd, etc, it runs on the 1st, the 2nd, etc....
My solution was to use another scheduling program and taskill SBBS. But, an option to stack requirements to limit a timed event would be cool.
Those requirements (months, days of month, days of week) are logically "AND"ed together, so in your example above, the event should only run on a Monday (with a day-of-month value of 1-7). Here's the actual code and I know it's a bit hard to read but I don't see anything wrong with it:
if(sbbs->cfg.event[i]->last==-1 ||
(((sbbs->cfg.event[i]->freq
&&
(now-sbbs->cfg.event[i]->last)/60>=sbbs->cfg.event[i]->freq)
|| (!sbbs->cfg.event[i]->freq
&&
(now_tm.tm_hour*60)+now_tm.tm_min>=sbbs->cfg.event[i]->time
&& (now_tm.tm_mday!=tm.tm_mday ||
now_tm.tm_mon!=tm.tm_mon)))
&& sbbs->cfg.event[i]->days&(1<<now_tm.tm_wday)
&& (sbbs->cfg.event[i]->mdays==0
||
sbbs->cfg.event[i]->mdays&(1<<now_tm.tm_mday))
&& (sbbs->cfg.event[i]->months==0
||
sbbs->cfg.event[i]->months&(1<<now_tm.tm_mon))))
The "last==-1" check is just a check to see if the event was forced. Otherwise, it will only run if the configured conditions are met (frequency, time, day of week, day of month, and month). And *all* the conditions that are not set to "any/all", indicated mostly with "==0" above, must be "true" for the event to execute. I guess I could setup a test case and see if I can reproduce the problem you're reporting.
Re: Re: No log entries in sbbsctrl for ftp/qwk uploads?<snip>
By: Digital Man to KenDB3 on Wed Sep 02 2015 07:08 pm
Those requirements (months, days of month, days of week) are logically "AND"ed together, so in your example above, the event should only run on a Monday (with a day-of-month value of 1-7). Here's the actual code and I know it's a bit hard to read but I don't see anything wrong with it:
The "last==-1" check is just a check to see if the event was forced. Otherwise, it will only run if the configured conditions are met (frequency, time, day of week, day of month, and month). And *all* the conditions that are not set to "any/all", indicated mostly with "==0" above, must be "true" for the event to execute. I guess I could setup a test case and see if I can reproduce the problem you're reporting.
I'll see if I can check it out too. I noticed after I set it up, I got the notification that my time was reduced for that whole week. BUT I just realized I didn't see the message today (and wasn't looking for it yesterday).
So I wonder if it was an odd fluke that changed for me with one of the more recent updates. I'll retest as well. I don't kick off the backup batch from SBBS, but I kick off another batch file from SBBS first that simply knocks everyone offline for a minute preceding the backup.
Apologies if this all turned out to be crazy talk o.O
~KenDB3
Re: Re: No log entries in sbbsctrl for ftp/qwk uploads?
By: Digital Man to KenDB3 on Wed Sep 02 2015 07:08 pm
<snip>Those requirements (months, days of month, days of week) are logically "AND"ed together, so in your example above, the event should only run on a Monday (with a day-of-month value of 1-7). Here's the actual code and I know it's a bit hard to read but I don't see anything wrong with it:
The "last==-1" check is just a check to see if the event was forced. Otherwise, it will only run if the configured conditions are met (frequency, time, day of week, day of month, and month). And *all* the conditions that are not set to "any/all", indicated mostly with "==0" above, must be "true" for the event to execute. I guess I could setup a test case and see if I can reproduce the problem you're reporting.
I'll see if I can check it out too. I noticed after I set it up, I got the notification that my time was reduced for that whole week. BUT I just realized I didn't see the message today (and wasn't looking for it yesterday).
So I wonder if it was an odd fluke that changed for me with one of the more recent updates. I'll retest as well. I don't kick off the backup batch from SBBS, but I kick off another batch file from SBBS first that simply knocks everyone offline for a minute preceding the backup.
Apologies if this all turned out to be crazy talk o.O
~KenDB3
I am totally not seeing the behavior anymore, and have no idea what caused me to see it before. Sorry, I really thought I knew what I was talking about there for a minute, lol.
Thanks for the clarification though, because that is exactly how I was expecting the functionality to work.
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 324 |
Nodes: | 10 (0 / 10) |
Uptime: | 114:27:55 |
Calls: | 499 |
Messages: | 218372 |