+19Apr20=======================================================================
+1. The long haul that is the mojo branch has started up again. It's something
+ to do during this lockdown.
+2. The problems and instabilities around running commands that worked in
+ forked processes, when used other than by normally logged in users (e.g.
+ in the local crontab), have been fixed.
+3. If a /spider/local_data/logout file is present then its contents will be
+ sent to the user on logout.
+4. Add the ability to sh/dx origin or ip (address).
+5. Retire the use of the deprecated Mojo::IOLoop::ForkCall in favour of using
+ the supported equivalent in Mojolicious 7.26 and above. Which means you
+ will need to upgrade Mojo to at least the version. The current version is
+ 8.36 and is known to work.
10Sep19=======================================================================
1. Improve DXSql database filtering to exclude most via <locator> type
reports.
You will need the following CPAN packages:
- sudo cpanm EV Mojolicious Sereal JSON JSON::XS
+ sudo cpanm EV Mojolicious JSON JSON::XS
# just in case it's missing
sudo apt-get install top
Please make sure that, if you insist on using operating system packages, that your Mojolicious is
-at least version 7.40. Mojo::IOLoop::ForkCall is NOT LONGER IN USE!
+at least version 7.26. Mojo::IOLoop::ForkCall is NOT LONGER IN USE! The current version at time
+of writing is 8.36.
Login as the sysop user.
$systime_days = $days;
$systime_daystart = $days * 86400;
}
+ IsoTime::update($systime);
DXCommandmode::process(); # process ongoing command mode stuff
DXProt::process(); # process ongoing ak1a pcxx stuff
- IsoTime::update($systime);
DXCron::process(); # do cron jobs
DXXml::process();
DXConnect::process();