Message boards : BOINC Manager : host name fixed?
Message board moderation
Author | Message |
---|---|
Send message Joined: 15 May 07 Posts: 54 |
is the hostname same for all clients? e.g. localhost? if not, is there an way to retrive it? thanks in advance |
Send message Joined: 16 Jun 07 Posts: 15 |
localhost is an alias for a hostname. It means *this* computer. The hostname can be specified in a number of ways. On Linux, type hostname to retrieve the current name. |
Send message Joined: 15 May 07 Posts: 54 |
ok, but or example, my hostname is 5000d but boinc in using localhost, using 5000d hasnt been able to connect |
Send message Joined: 15 May 07 Posts: 54 |
got linux, boinc 5.9.5, I'm asking cause of the command line boinc option |
Send message Joined: 14 Sep 06 Posts: 17 |
Okay, I'm having the same problem. On project sites, the name used for this Linux computer is 'localhost.localdomain' however typing in hostname in the shell provides a different and correct hostname. Is there some other place BOINC is expecting the name but didn't find? I'm a bit of a linux neophyte so I didn't bother until seeing this thread. |
Send message Joined: 29 Aug 05 Posts: 15561 |
Is there some other place BOINC is expecting the name but didn't find? It looks like it's stuck in the client_state.xml file. The <domain_name> entry is localhost.localdomain I'll test if changing it in my CS file will break things. ;-) That was a quick test. I changed the domain name to my computer name as root, saved the file, updated on one project and the entry was changed again to localhost.localdomain in client_state.xml ... I'll go ask a developer what is up with that. ;) |
Send message Joined: 29 Aug 05 Posts: 15561 |
Everyone, see Trac ticket 361 |
Send message Joined: 14 Sep 06 Posts: 17 |
Okay, I guess that means it wasn't a bad configuration on my end. Thanks for posting the ticket. EDIT: I looked this up and found this thread posted about the same issue over at SETI. Additional info about localhost.localdomain behavior is in this email in the debian mailing list. Lastly, the relevant code appears to be in client/hostinfo_network.C. I'm not sure I understand though, the hostname command in the shell apparently goes through the same function but returns differently. I used it without any arguments. Another concern - if the hostname gets changed, could it lead to a split host on the projects that cannot be merged? |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.