|FROM ||Brooklyn Linux Solutions CEO
|SUBJECT ||Re: [hangout] rsync problem
|From owner-hangout-desteny-at-mrbrklyn.com Tue Dec 18 11:58:05 2001
Received: (from mdom-at-localhost)
by www2.mrbrklyn.com (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id fBIGw5m04509
for hangout-desteny; Tue, 18 Dec 2001 11:58:05 -0500
Received: (from ruben-at-localhost)
by www2.mrbrklyn.com (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id fBIGw5t04503;
Tue, 18 Dec 2001 11:58:05 -0500
From: Brooklyn Linux Solutions CEO
Subject: Re: [hangout] rsync problem
In-Reply-To: from "Michael
M. L. Broggy" at "Dec 18, 2001 11:52:26 am"
To: "Michael M. L. Broggy"
Date: Tue, 18 Dec 2001 11:58:05 -0500 (EST)
CC: Ruben Safir , hangout-at-nylxs.com
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
Content-Type: text/plain; charset=US-ASCII
Reply-To: Brooklyn Linux Solutions CEO
List: New Yorkers Linux Scene
Admin: To unsubscribe send unsubscribename-at-domian.com to hangout-request-at-www2.mrbrklyn.com
You see it's running as a cronprocess so it is
not converting to the user who is runnign the program, but it
is running as the cron userinstead, which is likely root.
It's so stupid. I should be able to just set it with
And be done with it. It can obviously alter the ownership on delivery.
> On Tue, 18 Dec 2001, Ruben Safir wrote:
> > How do I set the remote settings?
> > I want everythign to convert to nobody.nogroup on the far side.
> Well, I don't know how you would do that - I just tried (as root) "rsync
> file mbroggy-at-remote.host:. -e ssh" (to use ssh since I don't have rsh on
> any of my boxes). It worked - even though the file was root.root on the
> local side, it became mbroggy.users on the other side.
> Changing it to nobody.nogroup automatically doesn't seem like it's
> possible unless you change it on the local side, which you're doing
> already. Why have it root.root on one machine and nobody.nogroup on the
It's really username.users on one side (where clients connect) and
they don't have accounts on the cleam machine, and we want the files
to be nobody.nogroup on the clean machine.
Wouldn't it be better to have them both the same if you're
> rsyncing anyway? Or maybe look into using something other than rsync?
> Best idea might be to code a perl script that'll take your input as
> arguments, record the original owner and group, change ownership, scp it
> over, do an md5sum on both sides to make sure it's all transferred nicely
> and then change the permissions back on the local side.
> Just a thought - I've never used rsync or r-anything...usually tar, gzip
> and scp. Reading the info on rsync seems to suggest it won't to
> owner/group/etc. transformations unless you rsync to user-at-host...hmm,
> unless you give "nobody" a password, that won't work, either. :/ Kind of
> defeats the point of the 'nobody' account if you give it a password ;)
New Yorker Linux Users Scene
Fair Use -
because it's either fair use or useless....