<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<font size="+1">There is a new version of the mojo branch out (build
402). There are some important changes to do with cleaning up the
users file and routing tables that you should look at. Details are
in the Changes file, an extract of which I enclose below:<br>
<br>
<font face="monospace">05Jan22=======================================================================<br>
1. Mark nodes that send PC92 K records as spider. These will
include VE7CC<br>
nodes. NOTE: there appear to be user records marked as user
or other sorts<br>
of node, which (now) are actually spider (compatible) nodes
and will be<br>
marked accordingly.<br>
2. Adjust nodes currently marked as spider nodes, but are
sending versions<br>
not in the spider range of versions on PC92 A records as
AK1A.<br>
3. Try to undo some damage where users have been autocreated
with similar<br>
attributes as nodes (locked out with privilege set to 1).
This will<br>
slowly fix this problem over time, but see item 4 for a 'big
bang'<br>
approach.<br>
4. It has come to my attention that there are a large number of
users (of<br>
all sorts) that have incompatible SSIDs. See 03Jan22/4 for
details.<br>
<br>
These are now being scrubbed out of the users file and also
will present<br>
as their normalised selves. If a -0* SSID is encountered
then, if the<br>
normalised version of that call is not present, it will be
renamed to<br>
that normalised call. If the normalised version of that user
record is<br>
already present, the un-normalised user record (-0*) will be
removed.<br>
5. Make export_users do a batch clean (as in 3. above) and also
get rid of<br>
(default) 12+ year old unaccessed user records and (default)
2+ year old<br>
"empty" records (with no qra/latlog/qth or handle).<br>
<br>
NOTE: if you do an manual export_users (as opposed to the
automatic one<br>
done once a week), do not be alarmed by the number of old
(i.e. more than<br>
12 years old) callsigns that it will get rid of. In my case
it was about<br>
~2/5th of the users file. Still left me with over 100,000
"active" users.<br>
<br>
In you are a bit twitchy about this, the code will copy the
current<br>
user_json and user_json.ooooo to user_json.keep and
user_json.backstop<br>
respectively. These files will never be overwritten unless
you remove one<br>
or both, when they will be regenerated on the next
export_user.<br>
04Jan22=======================================================================<br>
1. Fix issue in the RBN (and probably other places) with
callsigns that<br>
contain trailing / in callsigns like: OH0K/6, K2PO/7 etc.<br>
2. Regard strange callsigns like DR4W-HB (seen in skimmer spots)
as invalid.<br>
This *should be* something like HB9/DR4W or (spit) DR4W/HB9.<br>
3. Fix the (probably) spurious locking out of users that are
unknown to this<br>
node, that come in from other nodes. These create new user
records which<br>
where then automatically locked.<br>
03Jan22=======================================================================<br>
1. Allow overrides (on modern versions of perl) with things in
DXVars.pm, such<br>
$clusterport. This is really only of use for people trying to
run more than<br>
one instance of DXSpider on the same machine.<br>
2. Fix who command to make RBN connections as RBN and not USER.<br>
3. Prevent other nodes claiming that $myalias or $mycall is a
different type<br>
(user or node) from changing our route table and thence the
user type.<br>
4. Normalise callsigns of incoming connections to G1TST if
G1TST-0 or G1TST-00<br>
amd G1TST-2 if G1TST-02. There are 800+ instances of
callsigns with extra<br>
0 characters in the SSID in my users file. Allow SSIDs up to
99.<br>
</font><br>
NOTE: I am only enclosing the earlier changes because there are
mentions in the 05Jan22 changes. <br>
<br>
You will not affect the size of the users.v3j file with this
update and after doing an export_user (manually or automaticaly
once a week). But if you want to reduce the size of your user.v3j
file because of the large clearout of old or spurious SSID'd
callsigns then you can do this by:<br>
<br>
1. Do an manual 'export_user' in the console.<br>
2. Stop the node.<br>
3. cd /spider/local_data; perl user_json<br>
4. Start the node.<br>
<br>
This will *significantly* reduce the size of the users.v3j file.
And remember: an export_user will create two unchanging copies of
the latest and oldest versions of user_json. If in doubt, you can
recreate what you had before doing the export_user at any time. <br>
<br>
Please send all your brickbats to the usual email address. <br>
<br>
73+HNY Dirk G1TLH<br>
</font>
</body>
</html>