From: matt <matt@proweb.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] book chapters
Date: Tue, 1 Jul 2003 10:51:16 +0100 [thread overview]
Message-ID: <3F015994.2090001@proweb.co.uk> (raw)
In-Reply-To: <3F006BC5.4070309@nas.com>
>
> Where I have problems with matt's solution breaking down is when you
> have worker_5 creating random sets of files in a traditional
> hierarchy. Any subfolders he/she/it creates lose the rw permissions
> for the bosses group, and even with the sticky bit set for the group
> you lose those permissions the next level deep.
One of the problems we have is that I (in group wheel or as root) make
some file that someone else needs to be able to edit but often I forget
all about the permissions and it ends up "-rw-r--r-- matt wheel"
leaving the editors unable to edit it. And as they used to phone me at
the ungodly hours when I'm likely to be in bed (i.e. pre 10am) I needed
a solution
here's my inelegant solution from FreeBSD that does kind of the opposite
which is an interesting synergie because it uses wait_on which is a
program that gives access to the kqueue mentioned in another thread.
I don't know how big the queue can get but I have well over 500 files in
it across four directory trees
#!/usr/local/bin/rc
while () {
chown -R www:www /www/document_root
chmod -R g+w /www/document_root
wait_on `{find /www/document_root}
sleep 5
}
wait_on will return an index to which file has been changed/created for
more fine grained control
next prev parent reply other threads:[~2003-07-01 9:51 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 9:47 pac
2003-06-27 10:22 ` matt
2003-06-27 22:08 ` Joel Salomon
2003-06-27 22:12 ` Geoff Collyer, geoff
2003-06-27 23:39 ` boyd, rounin
2003-06-28 1:03 ` Scott Schwartz
2003-06-28 2:10 ` Dan Cross
2003-06-28 2:27 ` Dan Cross
2003-06-29 17:55 ` Jack Johnson
2003-06-30 11:17 ` matt
2003-06-30 13:43 ` ron minnich
2003-06-30 14:02 ` matt
2003-06-30 16:56 ` Jack Johnson
2003-06-30 17:16 ` boyd, rounin
2003-06-30 17:19 ` ron minnich
2003-06-30 17:24 ` ron minnich
2003-06-30 17:29 ` boyd, rounin
2003-06-30 18:40 ` rog
2003-06-30 23:16 ` Kenji Arisawa
2003-06-30 23:24 ` boyd, rounin
2003-07-01 1:44 ` David Presotto
2003-07-01 11:27 ` Kenji Arisawa
2003-07-01 11:32 ` David Presotto
2003-07-01 9:51 ` matt [this message]
2003-06-27 22:36 ` William Ahern
2003-06-27 22:28 Joel Salomon
2003-06-27 22:26 ` Geoff Collyer, geoff
2003-06-27 23:43 ` boyd, rounin
2003-06-27 23:46 ` Geoff Collyer, geoff
2003-06-28 0:53 ` Dennis Ritchie
2003-06-28 17:44 A. Baker
2003-06-29 4:38 ` Dennis Ritchie
2003-06-30 18:17 Richard C Bilson
2003-07-01 17:48 A. Baker
2003-07-02 0:27 ` Dennis Ritchie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F015994.2090001@proweb.co.uk \
--to=matt@proweb.co.uk \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).