Re: [zones-discuss] Script run from global zone into local zones - to shut them down

2008-05-09 Thread Jordan Brown (Sun)
Depends on whether you want to take the zone down *now* or want the gradual shutdown behavior of shutdown. Granted, -g0 is pretty abrupt. Sean McGrath - Sun Microsystems Ireland wrote: > > surely use zoneadm halt instead of zlogin ? >along with zoneadm list -p and grep for running zones..

Re: [zones-discuss] Script run from global zone into local zones - to shut them down

2008-05-09 Thread Jordan Brown (Sun)
Anne Moore wrote: > All > > I'm trying to write a script that will shutdown all zones from the local > zone. I'm not terribly good with scripting (yet), but thought many of > you would be. > > I need to run the command "zoneadm list" and then output each line to a > different variable to run

Re: [zones-discuss] Setting up SMC on a zone - possible?

2008-04-23 Thread Jordan Brown (Sun)
Anne Moore wrote: > Okay, that's good information. I can then install it manually and things > should work. I'll try in the morning. You could perhaps install all of the contents of that package (plus any other packages that are required and similarly situated), and that might well work. I'm pr

Re: [zones-discuss] Setting up SMC on a zone - possible?

2008-04-23 Thread Jordan Brown (Sun)
Jordan Brown (Sun) wrote: > You could perhaps install all of the contents of that package (plus any > other packages that are required and similarly situated), and that might > well work. ... but it would of course not be a supported conf

Re: [zones-discuss] Setting up SMC on a zone - possible?

2008-04-23 Thread Jordan Brown (Sun)
Anne Moore wrote: > Thanks for the reply. I am talking about the Solaris Management Console. I > have a whole-root zone and those two services are running. However, there is > no /usr/sbin/smc in my whole-root zone. It's like the whole-root > installation didn't even install it. Very odd. SUNWmcc

Re: [zones-discuss] new option - cpu-dedicated

2008-03-11 Thread Jordan Brown (Sun)
Mike Gerdts wrote: > Does updatemanager use patchadd -M under the covers? No. ___ zones-discuss mailing list zones-discuss@opensolaris.org

Re: [zones-discuss] Patches via Live Upgrade with 2 zones on Solaris 10 Update 4 failed

2008-03-06 Thread Jordan Brown (Sun)
Renaud Manus wrote: > Jordan Brown wrote: >> luupgrade -p does essentially that same set of operations. >> lumount+pca+luumount should be OK. > > But we (Sun) don't support it. True (which is why I said we'd prefer you used smpatch), but I believe that lumount + patchadd -R + luumount *is* supp

Re: [zones-discuss] Patches via Live Upgrade with 2 zones on Solaris 10 Update 4 failed

2008-03-06 Thread Jordan Brown (Sun)
[ Sorry if this is a repeat. I tried to abort it during the original send and haven't gotten my own copy, so I think something went a bit weird. ] Renaud Manus wrote: > Eric Ham wrote: >> I then ran the following Live Upgrade and PCA commands with no errors. >> >> lumake -s sol10-2007-08 -n d2

Re: [zones-discuss] Boot state completion?

2008-01-24 Thread Jordan Brown (Sun)
Christine Tran wrote: > who -r still works in a zone. > > [EMAIL PROTECTED]> zonename > zone1 > [EMAIL PROTECTED]> who -r > . run-level 3 Jan 24 14:53 3 0 S Yes, but apropos of our earlier discussion around milestone/multi-user-server, run level 3 doesn't mean "all services

Re: [zones-discuss] dbus in local zones

2008-01-15 Thread Jordan Brown (Sun)
Glenn Faden wrote: >> I understood that. What I didn't understand was why there wasn't a >> completely separate instance of the dbus-daemon running in each zone, >> with its own rendezvous file for communicating with clients in that >> zone. Why would you expect there to be cross-zone communic

Re: [zones-discuss] dbus in local zones

2008-01-14 Thread Jordan Brown (Sun)
Glenn Faden wrote: > I thought I answered that. The dbus-daemon is using a UNIX domain > rendezvous file in /tmp in the global zone. The non-global zones have > their own instances of /tmp, so the rendezvous file does not exist in > their namespace. Even if it did, there would be other problems

Re: [zones-discuss] dbus in local zones

2008-01-14 Thread Jordan Brown (Sun)
>> dbus-daemon cannot be run in non-global zones Sure sounds like the question is "why not?". ___ zones-discuss mailing list zones-discuss@opensolaris.org

Re: [zones-discuss] sharing "terminal server ports" to non-global zone

2007-12-18 Thread Jordan Brown (Sun)
Paul Davis wrote: > > Sounds like they want to access the local zone's console directly from a > terminal server? I don't believe there is a concept of that in the zones > model (of course, the local zone's console is normally started with > "zlogin -C zonename" from the global zone). Sure sou

Re: [zones-discuss] netmask warning, misconfiguration

2007-11-30 Thread Jordan Brown (Sun)
[EMAIL PROTECTED] wrote: > What does the "netmasks" entry in /etc/nsswitch.conf say? A common > issue is that a user changes their local /etc/netmasks file but their > the switch says to use something like "nis". Bingo! Thanks! >> (I also tried 172.20.0.0 on the theory that maybe it wanted me t

Re: [zones-discuss] netmask warning, misconfiguration

2007-11-30 Thread Jordan Brown (Sun)
Antonello Cruz wrote: > I would definitely run > > zonecfg -z int-sagent-1-z1 info > > to check what the zone thinks is the netmask. Doesn't display a netmask. > I suspect if you haven't defined the '/24' it will pick the default for > the address class. In this case, '/16' IIRC. > Sometimes d

Re: [zones-discuss] netmask warning, misconfiguration

2007-11-30 Thread Jordan Brown (Sun)
Antonello Cruz wrote: >> zoneadm: zone 'int-sagent-1-z1': WARNING: bge0:1: no matching subnet >> found in netmasks(4) for 172.20.46.188; using default of 255.255.0.0. > How did you setup the IP address for that zone? > > Did you use, in zonecfg: > zonecfg:int-sagent-1-z1:net> set address=172.20.4

[zones-discuss] netmask warning, misconfiguration

2007-11-29 Thread Jordan Brown (Sun)
I get: zoneadm: zone 'int-sagent-1-z1': WARNING: bge0:1: no matching subnet found in netmasks(4) for 172.20.46.188; using default of 255.255.0.0. but my /etc/netmasks (on both the global and local zone) looks good: 172.20.46.0255.255.255.0 (I also tried 172.20.0.0 on the theory that maybe