 UPDCUR.LIT question
#26213
12 Sep 18 10:03 AM
|
Joined: Nov 2006
Posts: 2,192
Stephen Funkhouser
OP
Member
|
|
OP
Member
Joined: Nov 2006
Posts: 2,192 |
I think I know the answer to this, but to verify my curiosity.
Does UPDCUR.LIT only update to the latest version of .LIT available regardless of the version of A-Shell it's executed under?
If so, would it not have the downside of updating to a .LIT that an older version couldn't run?
Stephen Funkhouser
Diversified Data Solutions
|
|
|
|
Re: UPDCUR.LIT question
#26214
12 Sep 18 12:21 PM
|
Joined: Jun 2001
Posts: 11,645
Jack McGregor
Member
|
|
Member
Joined: Jun 2001
Posts: 11,645 |
It uses different repositories depending on the version of A-Shell that it is executing under. For the most part, LITs are backwards and forwards compatible, so I often release LIT updates to both the 6.4 and 6.5 repositories. (If the update relies on a new A-Shell feature, the LIT usually checks the version and just doesn't implement that feature.)
But in a case where an update would fail under 6.4, in theory it would only be posted to the 6.5 repository and wouldn't be downloaded by UPDCUR running under 6.4.
Of course, if you share a SYS: directory between instances running both 6.4 and 6.5, that would defeat the safety mechanism. But that's exactly the environment that I normally run and test in, and I can't think of an instance of a 6.5-inspired update to a LIT or SBX that fails under 6.4.
|
|
|
|
Re: UPDCUR.LIT question
#26215
12 Sep 18 03:29 PM
|
Joined: Nov 2006
Posts: 2,192
Stephen Funkhouser
OP
Member
|
|
OP
Member
Joined: Nov 2006
Posts: 2,192 |
Thanks for the clarification.
Stephen Funkhouser
Diversified Data Solutions
|
|
|
|
Re: UPDCUR.LIT question
#26216
13 Sep 18 08:22 AM
|
Joined: Sep 2003
Posts: 4,135
Steve - Caliq
Member
|
|
Member
Joined: Sep 2003
Posts: 4,135 |
This does remind me to ask, Is there 65dev version on the horizon? A-Shell Version 6.5.1646.5
Current dir: DSK0:[1,4]
Repo: http://www.microsabio.net/dist/65dev/dsk0/001004/
Retrieving 001004.dir
Online repository not available for this directory
|
|
|
|
Re: UPDCUR.LIT question
#26217
13 Sep 18 10:28 AM
|
Joined: Jun 2001
Posts: 11,645
Jack McGregor
Member
|
|
Member
Joined: Jun 2001
Posts: 11,645 |
I think there must be a connection problem, as there is definitely a 65dev version, as you can see here (testing from an old 6.5.1639.3 install) ... .ver
-- A-Shell/32 Ver. 6.5.1639.3 Up and Running --
.updcur
UPDCUR 1.0(100) - Update current directory from online repository
A-Shell/32 Ver. 6.5.1639.3
Current dir: DSK0:[1,4]
Repo: http://www.microsabio.net/dist/65dev/dsk0/001004/
Retrieving 001004.dir
Checking current files against repository...
erase.lit ... ok
mdf62.lit ... ok
systat.lit ... ok
updcur.lit ... ok
3 files updated, 1 new files, 154 already current, 0 errorsI think that UPDCUR could benefit from an update to distinguish between failure to connect to the server, and no such directory, which is now on the list. But in the meantime, you can see the difference by activating the SOCKS trace, where you'll see a series of TCPX calls, starting with op 9 (connect) ... 4 08:24:42 <UPDCUR:6ee> tcpx: op=9, flags=1, sock=80, timer=1000, sockary=0
5 08:24:42 <UPDCUR:6ee> getsockopt returns 0, SO_ERROR = 0, buflen = 4
6 08:24:42 <UPDCUR:6ee> tcpx rtn: status=1, sock=1048 In the above excerpt we can see that the tcpx op 9 call returned status 1, sock=1048, meaning that it did connect. My guess is that for whatever reason, yours failed to connect on the first try. (Maybe a couple of retries might be in order too.)
|
|
|
|
Re: UPDCUR.LIT question
#26218
13 Sep 18 12:21 PM
|
Joined: Sep 2003
Posts: 4,135
Steve - Caliq
Member
|
|
Member
Joined: Sep 2003
Posts: 4,135 |
I shell try again , I never thought about it being a connection issue as got same under Linux in office and windows / ashell at home , maybe it’s the Atlantic Brixit firewall enabled early..
|
|
|
|
Re: UPDCUR.LIT question
#26219
08 Nov 18 06:21 PM
|
Joined: Jun 2001
Posts: 11,645
Jack McGregor
Member
|
|
Member
Joined: Jun 2001
Posts: 11,645 |
For what it's worth, UPDCUR.LIT has been updated to 1.0(103) with the following improvements: 1) It now reports whether files are new or simply being updated. 2) In the case where a file has a different hash but the local version is newer, it reports that. 3) If the hash is different but the local version is the same, it updates it. (Previously it may have considered it up to date if there was a version.) 4) If there are any errors, it repeats the scan, and keeps repeating it until 3 passes without any improvement in the number of errors. 5) If UPDCUR.LIT itself is updated, it will automatically repeat the scan. (Of course this won't have the first time, since you need to get the new version first.) UPDCUR 1.0(103) - Update current directory from online repository
A-Shell Version 6.5.1649.4
Current dir: DSK0:[1,4]
Repo: http://www.microsabio.net/dist/65dev/dsk0/001004/
Retrieving 001004.dir
Checking current files against repository...
kill.lit ... New: ok
systat.lit ... Upd: ok
zxpwin.lit ... [Local ver 1.0(8) > repo ver 1.0(7)]
1 file updated, 1 new file, 154 already current, 0 errors (The zxpwin.it 1.0(8) version above is a red herring just to test the version logic.) The 6.4 and 6.5 001004 repositories have been updated. (They are both actually the same at this point.)
|
|
|
|
|
