Hi Jon, > DTrace doesn't work in a zone until Solaris 10 08/07 so that's > why you're seeing this (I believe you're running Solaris 10 11/06). I think our systems engineers came up with this assumption (DTrace in zones works in 11/06) because after first noticing the problem they googled with "dtrace zone". The first hit is "Using DTrace in a Non-Global Zone" in the Solaris [Express] Sytem Administration Guide. The limitpriv property of the zonecfg command mentioned there is available since 11/06. I think this was the cause of the misunderstanding.
Maybe this historical "restriction" and DTrace-Zone-NFS restriction find their way into the documentation (or, if already there, to a more prominent place) ;) But maybe this is a stumbling block only to Solaris newbies like me and these restrictions are (at least in parts) well known to the pros. > I think this screws you for debugging objects which are running from > non-global zone based NFS mounts but doing the debugging in the > global zone. I think you have two solutions: > > 1) Upgrade to a later update of Solaris 10 and then you can do > your debugging all in the non-global zone. I'll definitely push this since 11/06 isn't that fresh anyway. Unfortunately it's a big shop with real-world restrictions and real-world systems engineers, so the mills grind slowly . . . > 2) Run off local filesystems in the non-global zone. My workaround is to copy the binaries to a local filesystem in the non-global zone after building them. It's a bit ugly but bearable. By all means it's way better than any other alternative. Once again, thank you for your support! Thomas -- This message posted from opensolaris.org _______________________________________________ dtrace-discuss mailing list [email protected]
