On 07/14 11:17 , Harry Mangalam wrote:
> > For Debian Linux, our company built a package to automate this
> > process. :) I don't know what kind of packaging tools are available
> > on OSX; but there must be someting.
>
> Want to share that package? :)
I've sent a copy off to Harry. If anyone els
On 07/14 11:17 , Harry Mangalam wrote:
> > For Debian Linux, our company built a package to automate this
> > process. :) I don't know what kind of packaging tools are available
> > on OSX; but there must be someting.
>
> Want to share that package? :)
sure; if I can find it. I didn't do the work
On Fri, 2006-07-14 at 10:07 -0700, Harry Mangalam wrote:
> The downside of this for larger installation tho is that it requires
> manual intervention to establish the shared ssh keys (for root!) to
> allow remote tar'ing of file, no?
Some distributions include an 'ssh-copy-id' script that does t
On Friday 14 July 2006 13:13, Carl Wilhelm Soderstrom wrote:
> On 07/14 10:33 , Harry Mangalam wrote:
> > But then doesn't this require even more manual intervention? Set
> > up the extra user, mod the sudoers file? Or is there a way to
> > automate this?
>
> For Debian Linux, our company built a
On 07/14 10:33 , Harry Mangalam wrote:
> But then doesn't this require even more manual intervention? Set up
> the extra user, mod the sudoers file? Or is there a way to automate
> this?
For Debian Linux, our company built a package to automate this process. :)
I don't know what kind of packa
On Friday 14 July 2006 12:43, Carl Wilhelm Soderstrom wrote:
> On 07/14 10:07 , Harry Mangalam wrote:
> > The downside of this for larger installation tho is that it
> > requires manual intervention to establish the shared ssh keys
> > (for root!) to allow remote tar'ing of file, no?
>
> you should
On 07/14 10:07 , Harry Mangalam wrote:
> The downside of this for larger installation tho is that it requires
> manual intervention to establish the shared ssh keys (for root!) to
> allow remote tar'ing of file, no?
you should be able to set up a special account on each client machine, which
use
The downside of this for larger installation tho is that it requires
manual intervention to establish the shared ssh keys (for root!) to
allow remote tar'ing of file, no?
(so does the rsyncd config, but in that case all you have to do is
place the "rsyncd.[conf|secrets]" files on the client. (w
Hi All,
Yes, you're right - Tiger's tar DOES work (a la the AppleDouble
approach of splitting of such files into file and ._file on the Linux
side).
Unfortunately, it was rsync that was the big win and attraction, but
I'll try the tar approach to see if it can do it well enough. We'll
be sup
Jacob is right,
>
> This doesn't mean you have to give up all hope in
> backuppc. I backup an
> OS X client just fine, but I use tar instead of
> rsync. Since it's on my
> local network, the extra bandwidth isn't too much of
> a problem.
I have even verified that the standard tar on OS X
works
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 13 Jul 2006 07:45:44 -0700
Harry Mangalam <[EMAIL PROTECTED]> wrote:
> On Wednesday 12 July 2006 11:25, misterpistolpete wrote:
> > Harry,
> >
> > Is your BackupPC server running OS X? I ask because
> > BackupPC probably will not work with the
On Wednesday 12 July 2006 11:25, misterpistolpete wrote:
> Harry,
>
> Is your BackupPC server running OS X? I ask because
> BackupPC probably will not work with the OS X version
> of rsync(d) unless you have a pure OS X environment.
> This is because OS X has it's own version of rsync to
> deal wit
Harry,
Is your BackupPC server running OS X? I ask because
BackupPC probably will not work with the OS X version
of rsync(d) unless you have a pure OS X environment.
This is because OS X has it's own version of rsync to
deal with resource forks.
http://en.wikipedia.org/wiki/Resource_fork
So even
Hi All,
Thanks to Ambrose Li for spotting my stupid editing mistake - the
rsyncd modules require a 'path = ' prefix to the directories to back
up. I can now rsync from the backuppc server to the client Mac from
the commandline, using the rsyncd method, but the backuppc-driven
backup is still
Hi All,
I'm trying to set up rsyncd to work on a MacBook Pro (Tiger/10.4.7),
rsync v 2.6.3. I have gotten it to work fine via rsync with shared
ssh keys on another Powerbook, but the rsyncd version is more
attractive because of the rsyncd.secrets file (no need to set up
another user or to req
15 matches
Mail list logo
