Thanks for the help today Alan. I also added '>/dev/null 2>&1' to the
end of each crontab line so I don't get any emails about innocuous
permission errors. Here is my crontab file (crontab -e) in case
anyone else finds this via search indexing:
0 * * * * /usr/local/bin/rsync -p -r /www/confluence-exports/SHIRO/
/www/incubator.apache.org/shiro >/dev/null 2>&1
5 * * * * find /www/incubator.apache.org/shiro -type f -exec chmod
g+rw {} \; >/dev/null 2>&1
5 * * * * find /www/incubator.apache.org/shiro -type d -exec chmod
g+rwx {} \; >/dev/null 2>&1
On Wed, May 19, 2010 at 3:59 PM, Alan D. Cabrera <[email protected]> wrote:
> Here's your new crontab entries we talked about:
>
> 0 * * * * (/usr/local/bin/rsync -p -r /www/confluence-exports/SHIRO/
> /www/incubator.apache.org/shiro)
> 5 * * * * (find /www/incubator.apache.org/shiro -type f -exec chmod g+rw {}
> \;)
> 5 * * * * (find /www/incubator.apache.org/shiro -type d -exec chmod g+rwx {}
> \;)
>
> On May 19, 2010, at 3:25 PM, Les Hazlewood wrote:
>
>> Hi team,
>>
>> I'm setting up a new (much nicer) site template for the Confluence
>> site export. This template requires static assets (images, css).
>>
>> Along with our maven generated site, which is also static, I'm
>> thinking we need a single directory in the web space which indicates
>> all static resources so we don't conflict with any Confluence-exported
>> content.
>>
>> I'm thinking we should have a top-level /static directory under which
>> all static content resides, including the Maven generated site.
>> Currently the maven generated site is located at /site which is a
>> little odd, since we already have a 'site'. Can we move it to
>> /static/mvnsite to parallel other static images? Thoughts?
>>
>> - Les
>
>
