CADENCE and ACL (Solaris)

P

PM

Guest
Hi,

Default behavior: CADENCE(Virtuoso,...) destroys existing ACLs :-(

Are ACL implemented in CADENCE and if so how to make use of them.

If not: are there any plans to change this in future releases?

Thanks
 
PM wrote:
Hi,

Default behavior: CADENCE(Virtuoso,...) destroys existing ACLs :-(

Are ACL implemented in CADENCE and if so how to make use of them.

If not: are there any plans to change this in future releases?

Thanks
I have here setups where the sticky bit on group is not always respected by some cadence programs. I could not find the pattern and don t know how to reproduce it, though.

I would not touch ACLs with a 10 foot, perfect insulator, 5th order, dominant pole anyway. Life is hard enough with plain ownerships/permissions. Are you doing this to have a better samba server ?
 
On Fri, 09 Apr 2004 17:42:13 +0200, fogh <cad_support@skipthisandunderscores.catena.nl> wrote:
I have here setups where the sticky bit on group is not always respected by some cadence programs. I could not find the pattern and don t know how to reproduce it, though.
pedantryAlert
I assume you don't mean the sticky bit, but the setuid (or setgid) bit. One of the things that
always irritates me is that this is often referred to as the "sticky" bit, but in fact the sticky bit
is something else altogether.

From the chmod(2) man page (on Sun):

If a directory is writable and has S_ISVTX (the sticky bit)
set, files within that directory can be removed or renamed
only if one or more of the following is true (see unlink(2)
and rename(2)):

o the user owns the file

o the user owns the directory

o the file is writable by the user

o the user is a privileged user

The sticky bit is the one that shows up as "t" in the ls -l output, and is often found on
the /tmp directory...

</pedantryAlert>

I would not touch ACLs with a 10 foot, perfect insulator, 5th order, dominant pole anyway. Life is hard enough with plain ownerships/permissions. Are you doing this to have a better samba server ?
ACLs are a nice idea, but not standard enough to be useful - they are rather platform
specific, unfortunately...

Andrew.

--
Andrew Beckett
Senior Technical Leader
Custom IC Solutions
Cadence Design Systems Ltd
 
Andrew Beckett wrote:
On Fri, 09 Apr 2004 17:42:13 +0200, fogh <cad_support@skipthisandunderscores.catena.nl> wrote:

I have here setups where the sticky bit on group is not always respected by some cadence programs. I could not find the pattern and don t know how to reproduce it, though.

pedantryAlert
I assume you don't mean the sticky bit, but the setuid (or setgid) bit. One of the things that
always irritates me is that this is often referred to as the "sticky" bit, but in fact the sticky bit
is something else altogether.

From the chmod(2) man page (on Sun):

If a directory is writable and has S_ISVTX (the sticky bit)
set, files within that directory can be removed or renamed
only if one or more of the following is true (see unlink(2)
and rename(2)):

o the user owns the file

o the user owns the directory

o the file is writable by the user

o the user is a privileged user

The sticky bit is the one that shows up as "t" in the ls -l output, and is often found on
the /tmp directory...

/pedantryAlert
Yes, What I meant was setgid. That sticky/setuid interpretation is a thing I once sorted out by looking up manpages, and I still make the mistake. Sticky mistake...
 

Welcome to EDABoard.com

Sponsor

Back
Top