I'm talking about the website preference interface on server builds 5.11 and 6.01.

Those are client version numbers; it's hard to know what server version matches with whatever client was available at the time. Instead, check the SVN revision shown on the project's server status page (it should be a 5-digit number).

Those are client version numbers; it's hard to know what server version matches with whatever client was available at the time. Instead, check the SVN revision shown on the project's server status page (it should be a 5-digit number).

Look on the CC message tab after a scheduler contact. It will show the server version, and in this case 511 on SAH nad 601 for EAH.

Alinator

Look on the CC message tab after a scheduler contact. It will show the server version, and in this case 511 on SAH nad 601 for EAH.

I know; that means "the client version that was available when the server was last updated", which is totally useless if clients aren't released often. I have just requested on BOINC mailing lists that the number shown on scheduler contact is changed to the SVN revision number.

To give you an idea of the difficulties, there are several versions 5.09 of the server version available, some of which do and some of which do not send 32-bit clients to 64-bit hosts.

I'm not sure if the client should show the SVN number (I know, you didn't ask that), but it would definitely make things easier if the projects would show somewhere on their main page which server version they use.

---

but it would definitely make things easier if the projects would show somewhere on their main page which server version they use.

It's on server_status.php page. However, that only shows for newer projects (created after the addition of the number), because server_status.php doesn't get updated when the rest of the server is updated (of course the number itself does).

PS: you may want to split these posts about version numbers into a separate thread...

Posts split off from Battery Preference as they may not belong there. If they do, we can always move them back. :)

---

It's OK with me, since it's a different backend issue than the battery prefs being broken. Although it does have a bearing due to making it hard to submit an accurate report of a problem.

The server should be identifying itself to the Client by its SVN Rev Number rather than the version number of the CC that happened to come along in the tarball it was built from. I don't see the problem with sending it to the client in place of the bogus CC version, unless it was was like 500 characters long or something like that. I mean even web servers identify their version for the most part if you ask them.

Also, I can't seem to find it (the SVNRN) on any of the server status pages for the projects I'm attached to and a dozen or so other projects I looked at as was reported here.

So as it stands a user/host doesn't really have a clue about what their talking to on the other end of the wire. Overall I'd have to say if you're not going to send the correct information in the contact session reply, it would be better to not send anything rather than the wrong information.

Alinator

I'm not sure if the client should show the SVN number (I know, you didn't ask that), but it would definitely make things easier if the projects would show somewhere on their main page which server version they use.

It would be a good idea for the client to report which build it is too.

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

It would be a good idea for the client to report which build it is too.

The client already shows which build number it is. In BOINC Manager it'll show in the Help->About BOINC Manager menu. In BOINC itself (the daemon) it shows in two ways, either by you right-clicking on the executable and looking at the properties, version number. Or by checking it through the command line, with the --version option (boinc --version)

It won't need to show which SVN revision it is running. Usually when a lot of changes have been added to the code, a new revision number will be released.

---

It would be a good idea for the client to report which build it is too.

The client already shows which build number it is. In BOINC Manager it'll show in the Help->About BOINC Manager menu. In BOINC itself (the daemon) it shows in two ways, either by you right-clicking on the executable and looking at the properties, version number. Or by checking it through the command line, with the --version option (boinc --version)

It's the first line on the messages too, so it's on the saved log file, on the Messages tab shown on the manager, and even available from boinc_cmd --get_messages (although that one is a total pain to use).

Both those methods only show the version number - not the revision number. If you are only dealing with stable releases that's all very well as no further changes are made to the source, but if you're running alpha/beta releases I think it would be a benefit.

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

Both those methods only show the version number - not the revision number.

I know. I was just listing more places where the version number can be found.

If you are only dealing with stable releases that's all very well as no further changes are made to the source, but if you're running alpha/beta releases I think it would be a benefit.

"Official" alpha versions have a version number too. Unless you compile from the development code directly, it wouldn't be a problem. However, it's definitely important for the server code. And anyway, how hard is it to add the revision number to the about box? ;)

I have created a trac ticket (my first) asking for this as a trivial enhancement :)

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1