At 01:42 PM 11/29/2000 -0600, you wrote:
>Just to be picky -- note that the cron job as literally listed will run
>once every minute, which can be a bit excessive. If /work has a lot of
>entries, the find job might take longer than a minute to complete, which
>means you're always thrashing your disk, which means your performance is
>going to suffer.
Bingo. I knew before I posted I'd get the cron "tip" :-). Oh well. I was hoping
someone would say something smart about perms and umask that I didn't already know :-)
JW
>-m
>
>"Todd A. Jacobs" wrote:
>>
>> On Wed, 29 Nov 2000, Jonathan Wilson wrote:
>>
>> > Any ideas? The point is to make everything created in the /work dir
>> > automatically have g+rwx.
>>
>> It's a umask problem. You'll probably need to set up a cron job such as
>> the following:
>>
>> * * * * * find /work ! -type d -exec chmod 664 \{\} \;
>> * * * * * find /work -type d -exec chmod 775 \{\} \;
>>
>>
>> to recursively set the correct permissions. Note that if you don't have
>> subdirectories (which require the execute bit set), you can just do:
>>
>> chmod g+rw /work/*
>>
>> Using a recursive chmod will unfortunately unset the execute bit on
>> directories, or perhaps set the execute bit on files which should be
>> executable. Find gives you much more flexibility.
>>
>> --
>> Todd A. Jacobs
>> Senior Network Consultant
>>
>> _______________________________________________
>> Redhat-list mailing list
>> [EMAIL PROTECTED]
>> https://listman.redhat.com/mailman/listinfo/redhat-list
>
>--
>Michael Jinks, IB // Technical Entity // Saecos Corporation
>"No one speaks English and everything's broken." -- T. Waits
>"Tom Waits would have made a decent sysadmin." -- M. Jinks
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
