'Best practices' question for a backup

[Joseph Kubik]

Then you are having trouble with rsync 'cause root can still read a file
marked chmod 000.
-Joseph-

On 9/22/05, Madison Kelly <linux-5ZoueyuiTZhBDgjK7y7TUQ at public.gmane.org> wrote:
>
> James Knott wrote:
> > Madison Kelly wrote:
> >
> >>Hi all,
> >>
> >> I've run into an ethical/best practices question that I wanted input
> >>from as many people as I could get on. I have a backup program that is
> >>aimed to be generally available to the public. That said, I need to be
> >>careful how I tell the program to work. In this case though, either
> >>decision I think could upset someone. So....
> >
> >
> > My take on backups, is that the person doing the backup should have the
> > appropriate rights to the file they're backing up. Otherwise, a backup
> > could be used to violate permissions. If other than user files are to
> > be backed up, they should be done under root or other appropriate
> > permissions.
>
> Thanks!
>
> The actual 'rsync' call is performed as root so 'rsync' runs as root and
> should, in turn, be able to backup anything 'root' has access to. This
> still seems to skip directories and files though where global access is
> not set to at least readable.
>
> Madison
> --
> The Toronto Linux Users Group. Meetings: http://tlug.ss.org
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/legacy/attachments/20050922/83b81d11/attachment.html>