sequence, which can have
unintended consequences when connected remotely.
My solution has been to use `zlogin -e\@ -C zonename`, which sets
the zlogin escape sequence to @., and prevents the aforementioned
unintended consequences. :)
-Tim
--
/\Timothy Kennedy
://blogs.sun.com/comay/entry/privilege_set_me_free
that explains the reasons for permissions additional to sys_time.
-Tim
--
Timothy Kennedy
SDE Infrastructure Operations Manager
Email: timothy.kenn...@sun.com
Phone: +1-703-636-0531 / x53151
AIM/Skype: tkSUNW
be correct in thinking that this will be OK for the branded zones?
That's correct. I have some solaris 8 zones running under cluster
control, where zonepath is zfs, and they're doing just fine.
Nothing special had to be done.
-Tim
--
Timothy Kennedy
SDE Infrastructure Operations Manager
Email
any non-trivial ACLs on the underlying ZFS,
so I can't say whether they work as expected.
-Tim
--
Timothy Kennedy
SDE Infrastructure Operations Manager
Email: timothy.kenn...@sun.com
Phone: +1-703-636-0531 / x53151
AIM/Skype: tkSUNW
___
zones-discuss
Timothy Kennedy wrote:
Nicolas Dorfsman wrote:
Which ACL model is then used ?
From: System Administration Guide: Solaris 8 Containers
( http://docs.sun.com/app/docs/doc/820-2914/gfjbk?a=view )
Using ZFS
Although the zone cannot use a delegated ZFS dataset, the zone can
reside
