similar to: List access to rsyncd.conf modules

Displaying 20 results from an estimated 7000 matches similar to: "List access to rsyncd.conf modules"

2011 May 27
3
Rsync "file too large (27)"
Hi, I'm getting the following error occasional and can't find out why; 05/14/2011 09:28:51 rsyncing /dbtmp to /dbtmp.new (1st pass) .... rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync: write failed on "/dbtmp.new/file.dmp": File too large (27) rsync error: error in file IO (code 11) at receiver.c(258) [receiver=2.6.9] rsync: connection
2003 May 14
1
remote rsyncd modules and --link-dest
Can anyone shed any light on what I should expect from rsync when the --link-dest option is invoked when the destination is a remote rsync module? i.e. rsync --archive --delete --link-dest=../dst_1/ /src/ user@host::xyz/dst_0 I almost expected to get a whole lot of hard links in dst_1 to unchanged files in dst_0... if I skip rsyncd on the server side (i.e. make the target
2007 Jul 16
1
rsyncd.conf
Hi, I have installed rsync on CentOS4, Installation went through ok and I tested it as well by copying a folder to mounted tap backup drive. But now I need to run rsync as daemon(server), trying to find /etc/rsyncd.conf file but there is no rsyncd.conf file exists under /etc directory. Having read online I found out that /etc/rsyncd.conf file needs to be manually created. Is there any sample
2003 Nov 25
1
unable to open configuration file "rsyncd.conf"
I'm getting an error trying to pull a file with ssh/rsync: $ rsync -e 'ssh -i .ssh/id_rsa' test@server.com::www/index.html index.html rsync: unable to open configuration file "rsyncd.conf": No such file or directory rsync error: syntax or usage error (code 1) at clientserver.c(502) rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync
2005 Feb 07
1
rsyncd.conf is not created although successful installation of rsync on debian but
Hi All, I have installed rysnc-2.6.3 on my debian linux ( 2.2.20-idepci #1 Sat Apr 20 12:45:19 EST 2002 i686). While configuration it was successful and i installed it without any error. Now, in default installation it should create rsyncd.conf as detault configuration file.. but it has not been created anywhere in system. root@jike:/tmp/temp/rsync-2.6.3# which rsync /usr/local/bin/rsync In
2004 Feb 24
2
ssh and rsyncd.conf
I am able to perform the following line rsync -rsh="/usr/bin/ssh" filename host:/dir/filename But I am not able to perform this rsync -rsh="/usr/bin/ssh" filename host:module_name where rsyncd.conf contains the following pid file = /var/run/rsyncd.pid log file = /var/log/rsyncd.log read only = false [module_name] path = /home/test comment =
2005 Mar 03
1
rsyncd.conf without --daemon?
Hello all, I'm not a total newbie, but probably close enough. I have tried to find the answer to this question, but have been unsuccessful. I'm testing out rsync over ssh using empty passphrases between 2 OpenBSD 3.5 boxes using rsync 2.5.7 (yes i know i should upgrade, but can't because of BSD ports issues). Everything seems to be working, but I'm very confused as to why it is
2003 Jun 23
1
any way to get --one-file-system in rsyncd.conf?
I would like to specify an entry in /etc/rsyncd.conf such that it operates on a --one-file-system basis always. The path will point to a filesystem mount point, but there is another filesystem that is mounted in a subdirectory. I want to back up only those files in the pointed to filesystem, and not the one mounted within (in that run, anyway). I do not see such an option in man rsyncd.conf. Is
2007 Jul 12
1
rsyncd.conf missing option akin to --one-file-system
It seems to me that rsyncd.conf does not provide an option akin to rsync's --one-file-system command line argument. If that is true, it seems like a bug of ommission, as I now face a use case where I need it. Is there maybe some technical reason for the ommission? Thanks, -- Lester Hightower
2014 Dec 17
0
[Bug 11013] New: [patch] Mention that privileges are dropped, when "use chroot" is enabled in rsyncd.conf manpage
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Only root can chown. If rsync isn't running as root then it ignores the --owner part of --archive. This also makes --numeric-ids inert. Simply put, if you aren't running as root then you can only create files owned by your UID. Rsync knows this. Rsync assumes that if you aren't root you didn't intend the --owner (or --group) part
2003 Dec 02
1
Size Limit in rsyncd.conf File?
I've got an rsyncd.secrets file with 59 accounts in it. Almost all these need to be enabled concurrently. My rsyncd.conf thus has an auth users field with upward of 50 values. I'm starting to wonder at what point I'll have maxed that field out, especially as we're taking on new accounts all the time. Incidentally, whether or not there is a limit, is it possible to do some
2011 Dec 12
2
[Bug 8655] New: link-by-hash: add 'link by hash dir' to rsyncd.conf
https://bugzilla.samba.org/show_bug.cgi?id=8655 Summary: link-by-hash: add 'link by hash dir' to rsyncd.conf Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: chris
2014 Oct 09
1
rsync filter parameter in rsyncd.conf file
I would like to push a file, /home/cfg/temp, from client to a server with rsync in daemon mode to /n2p/cfg directory. How should I set the filter/include/exclude parameters on the server side rsyncd.conf file so server will disallow receiving any files from the client other than /home/cfg/temp? -------------- next part -------------- An HTML attachment was scrubbed... URL:
2005 Aug 25
1
unable to open configuration file rsyncd.conf
Hello, Rsync is working great for me right now, using version 2.6.5 on two Solaris 9 V100 servers. Box A is the source and box B is the destination, and also box B is my rsync server box. Box A is a rsync client. Yesterdar from Box B I pulled 250 meg just fine from box A with rsync. Today from the client I want to just copy over to the server what files have changed today. So my command
2008 Apr 09
3
DO NOT REPLY [Bug 5381] New: make test fails without /etc/rsyncd.conf
https://bugzilla.samba.org/show_bug.cgi?id=5381 Summary: make test fails without /etc/rsyncd.conf Product: rsync Version: 3.0.2 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: email@cs-ware.de
2011 May 26
2
unexpected subfolder locaton in Maildir/.INBOX.subfolder
Hallo, I try to migrate existing imap server to dovecot 1.2 in debian squeeze if I connect to imap://user at host/INBOX Inbox works as expected and I get the content of Maildir/{cur,new,tmp} Maildir/.subfolder already exists if I connect to imap://user at host/INBOX.subfolder I get "folder not found" if I do a imap directory listing (raw mutt config, no subscriptions)
2002 May 10
1
Possible exclude bug in 2.5.5 in rsyncd.conf
Hello all, I've found some behavior in 2.5.5 that is contrary to the documentation in the man page. Specifically, I'm running an rsync server (i.e. from inetd with --daemon),and in the module definition I'm specifying the line "exclude nosyncdir". The documentation for rsyncd.conf indicates that this is exactly equivalent to using "--exclude nosyncdir" on the
2016 Mar 30
2
[Bug 11814] New: man-copy Make target missing rsync.1 and rsyncd.conf.5 dependencies
https://bugzilla.samba.org/show_bug.cgi?id=11814 Bug ID: 11814 Summary: man-copy Make target missing rsync.1 and rsyncd.conf.5 dependencies Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 Component: core
2008 Apr 23
1
DO NOT REPLY [Bug 5411] New: rsyncd.conf allow does not like CNAME
https://bugzilla.samba.org/show_bug.cgi?id=5411 Summary: rsyncd.conf allow does not like CNAME Product: rsync Version: 2.6.9 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: marc@perkel.com
2010 Jun 11
1
DO NOT REPLY [Bug 7510] New: rsyncd.conf: Default path=/ is dangerous
https://bugzilla.samba.org/show_bug.cgi?id=7510 Summary: rsyncd.conf: Default path=/ is dangerous Product: rsync Version: 3.0.7 Platform: Other OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: pepper at reppep.com