On Sat, 2002-12-28 at 18:59, John Nichel wrote:
> Yeah, I know how groups / permissions work. What I was wondering, is
> there a way to set a sticky bit recursively, so that no matter what the
> default group of a user is, any file or directory that the user creates
> in a certa
Yeah, I know how groups / permissions work. What I was wondering, is
there a way to set a sticky bit recursively, so that no matter what the
default group of a user is, any file or directory that the user creates
in a certain directory will be set to the group of that directory. I
don't
On Saturday 28 December 2002 01:00 pm, John Nichel wrote:
> Hello fellow RedHatters,
>
>Can someone tell me if it's possible to set a sticky bit recursively
> on a directory? What I'm looking to do is to have multiple users
> creating files and directories in a certai
Hello fellow RedHatters,
Can someone tell me if it's possible to set a sticky bit recursively
on a directory? What I'm looking to do is to have multiple users
creating files and directories in a certain place, and I want those
files / directories to be group readable / writ
> I am not really certain if I understand this.
> Is this a command "qpasswd".
> Do i need to place the sticky bit on the directory and not the file?
> This may all be moot because I am doing this through Samba. Does that
> make a difference? Do I need to add something
I am not really certain if I understand this.
Is this a command "qpasswd".
Do i need to place the sticky bit on the directory and not the file?
This may all be moot because I am doing this through Samba. Does that make
a difference? Do I need to add something to my samba config
ack in
> and chgrp and chown.
> How can I stop this from happeing?
> Will setting the sticky bit help?
> Doug
>
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
> https://listman.redhat.com/mailman/listinfo/redhat-list
H
chown.
How can I stop this from happeing?
Will setting the sticky bit help?
Doug
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert P. J. Day wrote:
>> >i understand that you can set the sticky bit on a directory so that
>> >everything created in that directory will be set to that group, but what i
>> >don't know how to do, is make that r
right--only who is left.
- bertrand russell
- Original Message -
Sent: Tuesday, July 02, 2002 12:18 PM
Subject: Re: chmod: sticky bit
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA1
|
| daniel wrote:
|
| >i understand that you can set the sticky bit on a directory so that
| >ever
On Tue, 2 Jul 2002, David Talkington wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> daniel wrote:
>
> >i understand that you can set the sticky bit on a directory so that
> >everything created in that directory will be set to that group, but what i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
daniel wrote:
>i understand that you can set the sticky bit on a directory so that
>everything created in that directory will be set to that group, but what i
>don't know how to do, is make that recursive.
# chmod -R 2775 .
Thereaf
i understand that you can set the sticky bit on a directory so that
everything created in that directory will be set to that group, but what i
don't know how to do, is make that recursive.
someone out there wanna help me out?
___
Redhat
print
However be sure that you understand its security implications. If you are
using SAMBA, use its configuration to force a user/group when accessing
the directories, and make the directories/files chmod to 755/644 (you
won't need the sticky bit anymore).
cheers,
Hossein
--
To unsubscrib
On Wed, Dec 01, 1999 at 05:47:16PM -0600, Stephen Hargrove wrote:
| Okay, I've created a little problem on my system. I have a partition
| that is shared among several different offices, so I set the
| permissions as follows:
|
| chmod -R 1666 *
|
| This resulted in all of the directories and f
On Wed, Dec 01, 1999 at 05:47:16PM -0600, Stephen Hargrove wrote:
>
>Okay, I've created a little problem on my system. I have a partition
>that is shared among several different offices, so I set the
>permissions as follows:
>
>chmod -R 1666 *
Directories typically are 755.
Okay, I've created a little problem on my
system. I have a partition that is shared among several different offices,
so I set the permissions as follows:
chmod -R 1666 *
This resulted in all of the directories and files having the
following permissions:
drw-rw-rwT directoryname
-rw-rw
n m,ore
> than one development group say, and default to dev1, when I work in the
> dev2 source tree, all the fiels I create have the group dev1. Bummer. The
> dev2 boys may not be able to use them properly. So, the beauty of the user
> provaye group scheme is that you set the sticky bit to
er 01, 1999 9:06 AM
To: '[EMAIL PROTECTED]'
Subject: Re: Sticky bit (wasL RE: LOGIN program)
You are misreading the man page. The t switch uses swap, the s switch sets
the user or group ID on execution.
I'm probably going to do a lousy job of explaining it, but I'll give it a
all the fiels I create have the group dev1. Bummer. The
dev2 boys may not be able to use them properly. So, the beauty of the user
provaye group scheme is that you set the sticky bit to control the group
id on all files under a directory. So if the dir /share/dev2 has the
sticky bit set (with the grou
Would someone please clearify what the purpose of the "sticky" bit is and
how it is used? I understand the concept of the set{u,g}id bits, but this
one is strange. I don't see how saving a program on the swap device would
be beneficial unless the swap device was faster than the
21 matches
Mail list logo
