Jeff Victor's Blog: Patching Zones Goes Zoom!


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS Jeff Victor's Blog: Patching Zones Goes Zoom!
# 1  
Old 04-09-2009
Jeff Victor's Blog: Patching Zones Goes Zoom!

Accelerated Patching of Zoned Systems: This blog entry discusses methods which can be used to reduce application downtime during patching.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Solaris

Need help in patching with lu on SVM+ZFS FS with zones

Hello, I need help in understanding, how lu can work on Solaris-10 on this server. I can detach mirror metadevices of LVM, but zpool looks confusing, which mirror I should break. server-app01 # : |format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN300G cyl... (0 Replies)
Discussion started by: solaris_1977
0 Replies

2. Solaris

Solaris Global/Zones patching

Issue is : We have Solaris Global with 12 Zones and some have 15 Zones. All the OS version are10. Is it possible to apply patch at Zone level instead of patching at Global level? Please let me know. (10 Replies)
Discussion started by: baladelaware73
10 Replies

3. Solaris

Help req for Patching on Solaris 10 Zones

Hi Experts, Can advise on this: Global zone running on solaris 10, & the local zones on top running on solaris 9, but we need to patch the solaris 9 local zones & also the solaris 10 global zone. Which should be patched first to avoid any crash in case, first local zones... (1 Reply)
Discussion started by: fizan
1 Replies
Login or Register to Ask a Question
NSS-MYHOSTNAME(8)						  nss-myhostname						 NSS-MYHOSTNAME(8)

NAME
nss-myhostname - Provide hostname resolution for the locally configured system hostname. SYNOPSIS
nss-myhostname.la DESCRIPTION
nss-myhostname is a plugin for the GNU Name Service Switch (NSS) functionality of the GNU C Library (glibc) providing hostname resolution for the locally configured system hostname as returned by gethostname(2). Various software relies on an always-resolvable local hostname. When using dynamic hostnames, this is usually achieved by patching /etc/hosts at the same time as changing the host name. This however is not ideal since it requires a writable /etc file system and is fragile because the file might be edited by the administrator at the same time. nss-myhostname simply returns all locally configured public IP addresses, or, if none are configured, the IPv4 address 127.0.0.2 (which is on the local loopback) and the IPv6 address ::1 (which is the local host) for whatever system hostname is configured locally. Patching /etc/hosts is thus no longer necessary. To activate the NSS modules, myhostname has to be added to the line starting with "hosts:" in /etc/nsswitch.conf It is recommended to put myhostname last in the nsswitch.conf line to make sure that this mapping is only used as fallback, and any DNS or /etc/hosts based mapping takes precedence. EXAMPLE
# /etc/nsswitch.conf passwd: compat group: compat shadow: compat hosts: files dns myhostname networks: files protocols: db files services: db files ethers: db files rpc: db files netgroup: nis To test, use glibc's getent tool: $ getent ahosts `hostname` ::1 STREAM omega ::1 DGRAM ::1 RAW 127.0.0.2 STREAM 127.0.0.2 DGRAM 127.0.0.2 RAW In this case the local hostname is omega. SEE ALSO
systemd(1), systemd-logind.service(8), logind.conf(5), loginctl(1), pam.conf(5), pam.d(5), pam(8), pam_loginuid(8) systemd 208 NSS-MYHOSTNAME(8)