On Mon, 14 Nov 2011, Mike Brown wrote:
> I can't run it as root, as root login via ssh is not allowed for security
> reasons.
>
PMFJI, but there *are* secure ways to allow root login - check out "forced
command only".
We run a number of rsnapshot/rsync jobs as root, but the only command
allowed i
On Mon, Nov 14, 2011 at 01:15:49PM -0500, Kevin Korb wrote:
> The main thing I wanted to show you was how to setup sshd to only allow
> root to log in via an ssh key and to restrict that ssh key to only being
> allowed to run rsync. That is much easier and more secure than setting
> up rsyncd with
On Mon, Nov 14, 2011 at 01:15:49PM -0500, Kevin Korb wrote:
> There was more in there than just sudo or rsyncd. In fact the FAQ
> advises against using sudo.
Ya, I saw that. It suggested changed to ssh for root to get it. The point
was that configuration of some sort was needed, no matter which
There was more in there than just sudo or rsyncd. In fact the FAQ
advises against using sudo.
The main thing I wanted to show you was how to setup sshd to only allow
root to log in via an ssh key and to restrict that ssh key to only being
allowed to run rsync. That is much easier and more secure
On Mon, Nov 14, 2011 at 12:42:55PM -0500, Kevin Korb wrote:
> http://www.sanitarium.net/rsyncfaq/#sudo
You either set up a rsyncd.conf file (easily done) and run rsync as a daemon
or set up sudo. I don't have sudo set up, so 6 of one, half dozen of the
other :-)
> This might be a good idea. It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/14/11 12:38, Mike Brown wrote:
> On Mon, Nov 14, 2011 at 10:36:39AM -0500, Kevin Korb wrote:
>> rsync -avzH host:/path/ /path/
>>
>> No new daemon or config file needed.
>
> That is how I started out. But, when run as me, it will not copy over
On Mon, Nov 14, 2011 at 10:36:39AM -0500, Kevin Korb wrote:
> rsync -avzH host:/path/ /path/
>
> No new daemon or config file needed.
That is how I started out. But, when run as me, it will not copy over files
that belong to other users.
I can't run it as root, as root login via ssh is not allo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Also, for a one time thing it is generally much easier to run rsync over
ssh than it is to setup the rsync daemon and config file...
rsync -avzH host:/path/ /path/
No new daemon or config file needed.
On 11/14/11 05:02, Paul Slootman wrote:
> On Mon
On Mon, Nov 14, 2011 at 11:02:29AM +0100, Paul Slootman wrote:
> Did you note the fact that the rsync daemon will by default do its work
> as user "nobody"? Search for "uid" in the rsyncd.conf manpage.
Nope, I did not. Will go looking, Thanks.
MB
--
e-mail: vid...@vidiot.com | vid...@vidiot.n
On Mon 14 Nov 2011, Mike Brown wrote:
>
> For the most part, all of the directories are being copied, but there are
> files that it refuses to copy. For example:
>
> -rw--- 1 brown146 Jul 31 20:58 .TTauthority
>
> Any file that is 600 it will leave behind and list it as permis
First time posting to this mail list. Be gentle :-)
Project: Building new Linux Fedora server to replace the existing Solaris 10
x86 server.
Rsync is being used to transfer files from the current server to the new
server. The rsync daemon didn't want to start on the older server via in
First time posting to this mail list. Be gentle :-)
Project: Building new Linux Fedora server to replace the existing Solaris 10
x86 server.
Rsync is being used to transfer files from the current server to the new
server. The rsync daemon didn't want to start on the older server via in
Hi,
I'm using rsync to copy and sync a directory of about 25,000 files
across two machines.
I used rsync to make an initial copy, from machine 1 to machine 2,
and then syncing back incremental changes from machine 2 to machine 1.
On the initial copy from machione 1 to machine 2, I found that a
13 matches
Mail list logo
