Hi!
playing with --include, --exclude, and --exclude-from=file I found these
not working:
xcnlm00s:/etc/adsm/script # rsync -navx --include="*/" --exclude="*" -e
ssh newsfeed:/
receiving file list ... done
wrote 29 bytes read 28605 bytes 3014.11 bytes/sec
total size is 0 speedup is 0.00
xcn
Need more information - the rsyncd.conf, for instance. The hosts.allow,
for another.
You're best to start off with a basic conf file, and add complications one
at a time until it breaks, then figure out what was wrong with that single
item. Running rsyncd from inetd really helps with that - e
Alternatively, if the users need to do the writing themselves
(checkpointing a project, for instance), you should set aside a seperate
module for each one. It will be a hassle for you to take care of the
passwords, and they will be stored in plain text, though (one hopes)
secure. If they're
I'm not sure what the problem is. Here's a snip of my log (very similar
setup, but from server to remotes):
2001/05/17 14:26:59 [29226] rsync on ToolSyncModules/ToolSyncModuleList
from irvnetsvr (134.27.9.31)
2001/05/17 14:27:00 [29226] wrote 23292 bytes read 128 bytes total size
23179
2001/
It seems to me that there must be a more fundamental problem with the
security model of that backup system if users had the ability to read each
other's files. Even with a "write only" option, they can overwrite each
other's files, right? What if somebody overwrite a crucial file in
somebody els
On Fri, Feb 22, 2002 at 10:08:37PM -0800, Martin Pool wrote:
> On 22 Feb 2002, Albert Chin <[EMAIL PROTECTED]> wrote:
> > I have the following module defined in rsyncd.conf:
> > [updates]
> > list = no
> > hosts allow = foo
> > path = /ext/updates
> > exclude = incoming
> >
> >
Check the server's log. By default it goes to syslog, but you can also
make it go to a file with a "log file = " in rsyncd.conf. For security
reasons the rsync daemon mode doesn't give away much information to the
client.
Make sure rsyncd.conf is not group-writable, that's a common problem.
-
