On Thu, 11 Dec 2014, Alex McWhirter wrote:

| Yea, some services picked it up but others did not. It seems the 
identity/node service does not have the config variable set for nodename. I 
attempted to set it but received and error saying that the variable didn't 
exist.
| 
| I don't think this was ever an intended function for a zone.

Well it does on solaris 10 so I thought it might be worth a try.
.....
# uname -n
ftp22
# zonename
ftp
# cat /etc/nodename
ftp22
#
.....

| 
| Sent from my iPhone
| 
| > On Dec 11, 2014, at 1:30 AM, Tim Rice <[email protected]> wrote:
| > 
| >> On Wed, 10 Dec 2014, Alex McWhirter wrote:
| >> 
| >> I have a small cluster of servers hosting zones over multiple VLAN’s. I 
would like to name the zones so that they don’t run into naming collisions. For 
example, instead of “web0” i would like to name them “2049_web0” and 
“2050_web0”. The problem is that this set’s the hostname to “XXXX_web0”. Is 
there a way to change the hostname to be something different than the zone name?
| >> 
| >> I had a look at /etc/nodname and it is an empty file when used in a zone.
| > 
| > What happens if you put the hostname you want in /etc/nodname ?
| > 
| > 
| > -- 
| > Tim Rice                Multitalents
| > [email protected]
| _______________________________________________
| OmniOS-discuss mailing list
| [email protected]
| http://lists.omniti.com/mailman/listinfo/omnios-discuss
| 
| 
| 

-- 
Tim Rice                                Multitalents    (707) 456-1146
[email protected]
_______________________________________________
OmniOS-discuss mailing list
[email protected]
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Reply via email to