On 11/13/18 2:03 PM, Rich Shepard wrote:
On Sun, 11 Nov 2018, Rich Shepard wrote:
Yesterday rsync copied ~/ from the current desktop (salmo) to the new
desktop (baetis) using this command from ~/ on the new desktop: rsync -av
salmo: .
I gave up trying to find a reason for this behavior
On Sun, 11 Nov 2018, Rich Shepard wrote:
Yesterday rsync copied ~/ from the current desktop (salmo) to the new
desktop (baetis) using this command from ~/ on the new desktop: rsync -av
salmo: .
I gave up trying to find a reason for this behavior and re-ran ssh-keygen,
ssh-agent, and
On Tue, Nov 13, 2018 at 8:56 AM Rich Shepard
wrote:
> On Tue, 13 Nov 2018, Smith, Cathy wrote:
>
> > I apologize for intruding.
>
> Cathy,
>
>Apologies not necessary.
>
+1 to this: we just jump in whenever we feel we can be helpful.
Occasionally this leads to confusion and chaos, but it's
On Tue, 13 Nov 2018, Smith, Cathy wrote:
I apologize for intruding.
Cathy,
Apologies not necessary.
I've been following this conversation and now I'm confused. Is the issue
the use of keys to lock down access, or the use of rsync in general?
The issue is that I set up ssh on the new
-boun...@pdxlinux.org [mailto:plug-boun...@pdxlinux.org] On Behalf Of
Rich Shepard
Sent: Tuesday, November 13, 2018 5:54 AM
To: Portland Linux/Unix Group
Subject: Re: [PLUG] rsync: worked once now perms error
On Mon, 12 Nov 2018, wes wrote:
> You said "rather than ssh" - did you test ss
On Mon, 12 Nov 2018, wes wrote:
You said "rather than ssh" - did you test ssh again after you started
getting this error? What command and parameters do you use to make the ssh
connection?
wes,
When rsync failed to connect Sunday I used 'ssh -vv ...' to test since
adding the verbose
On Mon, Nov 12, 2018 at 11:09 AM Rich Shepard
wrote:
> On Sun, 11 Nov 2018, Rich Shepard wrote:
>
> > Yesterday rsync copied ~/ from the current desktop (salmo) to the new
> > desktop (baetis) using this command from ~/ on the new desktop: rsync -av
> > salmo: .
>
>Today I tried using rsync
On Sun, 11 Nov 2018, Rich Shepard wrote:
Yesterday rsync copied ~/ from the current desktop (salmo) to the new
desktop (baetis) using this command from ~/ on the new desktop: rsync -av
salmo: .
Today I tried using rsync again rather than ssh. I don't know where to
look to see the error:
$
I would not think that you want to really set any directory in /opt as 777.
So that anything could write or delete stuff there.
-T
On Mon, Nov 12, 2018, 2:17 AM david On 11/11/18 7:49 AM, Rich Shepard wrote:
> >Yesterday rsync copied ~/ from the current desktop (salmo) to the new
> >
On Sun, 11 Nov 2018, david wrote:
Are you able to connect to salmo using the password, and is it configured
to accept the ED25519 key format?
David,
I use a passphrase and added it to ssh-agent yesterday. Both before and
after I was able to use rsync and scp to move files over from one to
On 11/11/18 7:49 AM, Rich Shepard wrote:
Yesterday rsync copied ~/ from the current desktop (salmo) to the new
desktop (baetis) using this command from ~/ on the new desktop: rsync -av
salmo: .
/opt on both hosts have perms 777.
However, when I try to copy the /opt partition from
Yesterday rsync copied ~/ from the current desktop (salmo) to the new
desktop (baetis) using this command from ~/ on the new desktop: rsync -av
salmo: .
/opt on both hosts have perms 777.
However, when I try to copy the /opt partition from salmo to baetis I get
a permission denied
12 matches
Mail list logo
