similar to: --log-file not overriding "log file"

I'm using Rsync 3.0.5 between two Debian boxes. I have an rsync script setup that uses --log-file=mylogfile.log and also I have specified --log-file-format=whatever. But I can't seem to get the --log-file-format to be recognized. I don't get any sort of errors, but the log format that I get is just the default, no matter how I change the format option. Just for simplicity's

Greetings - In my logwatch report this morning I noticed reference to an attempt to connect to rsync from an external IP address. It doesn't appear that the connection was successful based on correlating information between /var/log/secure and /var/log/messages. But I am looking for some suggestions for implementing more preventative measures, if necessary. The log information from

In Rails 2.3.x, you can override render_optional_error_file like so: # ApplicationController.rb protected def render_optional_error_file(status_code) render :template => "errors/500", :status => 500, :layout => ''application'' end However, Rails 3 no longer has render_optional_error_file. Instead, you need to overriderescue_action_in_public, which I do:

Hi All, I must not understand the uid/gid line in rsyncd.conf. If someone could briefly point out where I've gone wrong, I'd appreciate it. I've created a special user to backup a server which has some users who don't want all their files backed up, so I'm trying to address their concerns by using the uid= and gid= lines in rsyncd.conf to have the rsyncd run with

Hi I am wondering if there is any way to change the file permission of "rsync.log" and "rsyncd.lock" via rsyncd.conf. Most likely the "lock" file is not possible, but maybe the other file is possible. The reason I am asking is because if I UserA runs rsync, then UserB won't be able to write to rsync.log file since its owned by UserA and readable only to UserB.

I have the latest rsync running on mandrake official 10. At 2:30 I run rsync --daemon from cron to run an offsite backup for all my customers. At 8:00 I run killall rsync. However my log files show the following: 2004/04/20 02:00:00 [2702] rsyncd version 2.6.0 starting, listening on port 873 2004/04/20 02:00:59 [2707] rsyncd version 2.6.0 starting, listening on port 873 2004/04/20

Hi, I am using rsyncd server. I have the configuration in /etc/rsyncd.conf. I have included each modules section for each client.I want to have the log files of all activity in separate files for each client instead of in the global log file.Can sombody help me. /etc/rsyncd.conf ============================= #### rsyncd.conf file #### uid = backup gid = backup #pid file =

I run a CentOS/Fedora mirror with rsync access. I have the following rsyncd.conf file: read only = true transfer logging = true pid file = /var/run/rsyncd.pid log file = /var/log/rsyncd.log dont compress = * [Fedora] path = /var/ftp/pub/mirrors/fedora comment = Fedora mirror [CentOS] path = /var/ftp/pub/mirrors/centos comment = CentOS mirror My problem is that

hello, running an rsyncd server I get the following into the error log when trying to sync on a module : (...) Mar 15 15:32:44 xxxxxx rsyncd[5202]: building file list Mar 15 15:34:55 xxxxxxxxx rsyncd[5202]: rsync: writefd_unbuffered failed to write 4092 bytes to socket [sender]: Connection reset by peer (104) Mar 15 15:34:55 xxxxxxxxxx rsyncd[5202]: rsync error: error in rsync protocol data

I am running rsync version 2.56 in daemon mode on a server running Redhat 8.0. When I check my log file (located in /var/log/rsyncd.log), the only lines I see have to do with the server starting up, like so: 2003/09/11 16:53:42 [15025] rsyncd version 2.5.6 starting, listening on port 873 I would like to see output relating to connections, usernames etc., so I set up the following rsyncd.conf

Hi list, I just setup my first rsyncd server and all is working well as far as file syncing goes. However, I am a bit baffled by the fact that some of the log entries in the rsyncd.log file are entered in local time and other are entered in GMT. Here is a sample: file upload: ============ 2009/03/01 15:15:49 [22641] connect from UNKNOWN (xxx.xxx.xxx.xxx) 2009/03/01 23:15:49 [22641] rsync to

https://bugzilla.samba.org/show_bug.cgi?id=2455 Summary: rsync --daemon segfaults if "log file = <file>" dir does not exist Product: rsync Version: 2.6.3 Platform: Sparc OS/Version: Solaris Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

I've only just seen the response from May 9, as I'm not enrolled in the list (too much mail already!). Here is a cut-down example as requested, showing the same behaviour: Script started on Fri May 23 15:18:37 2003 15:18 [220](H:root@Edelfelt)/tmp: ls -l /tmp/testdir total 32 -rw-r----- 1 root other 9 May 23 15:15 both -rw-r----- 1 root other 7 May 23 14:59

I'm having trouble getting rsync to output the log into common log format. My web statistics program Webalizer (www.webalizer.org) wants the logs in Common Log Format (httpd.apache.org/docs/mod/mod_log_common.html). Briefly, that's a string host ident authuser date request status bytes subject to some conditions (for instance, the date is in square brackets). My rsyncd.conf file has

(As I was composing this, the 2.6.1 release notice on the rsync list rolled in. The quoted source, below, hasn't changed, so I'll leave the 'pre-1' references unchanged...) I have a situation where an error message seems to be sent from the daemon to the client, but none is logged in the daemon's log. Daemon is 2.6.1pre-1, with --timeout=3600, light CPU load. Client is

Hi, When using rsync-3.0.2 through 3.0.5, I get this error on a large dataset syncing from machine-a to machine-b: $ /bin/rsync -aHSz /local/. machine-b:/local/. invalid len passed to map_ptr: -1737287498 rsync error: error in file IO (code 11) at fileio.c(188) [sender=3.0.5] This happens no matter which side initiates the connection, so this fails in the same way: $ /bin/rsync -aHSz

Just upgraded from rsync 2.6.2 protocol version 28 to 2.6.3 protocol version 28. Linux kernel upgraded from 2.6.5-1 to 2.6.9-11. From the client side, I issued... rsync -av web::app_web /app > /dev/null From the server side, the config shows... [app_web] comment = Moving webs Inside & Outside path = /app auth users = root secrets file = /etc/rsyncd.secrets read only = true

I got rsyncd v2.6.6 protocol version 29 running on Suse Enterprise Server 10. Here's what my /etc/rsyncd.conf looks like - max connections = 0 log format = %a %h %o %f %l %b log file = /var/log/rsync/rsync.log [nibbler] path = /backup/nibbler comment = nibbler read only = no use chroot = no timeout = 3600 transfer logging = yes [remote] path = /backup/remote/ comment = remote read only = no

I'm trying to get over an exasperating problem with rsync 2.5.7, but I'm not making any headway. The nut of the problem is that the rsync daemon seemingly ignores the "syslog facility" configuration when running in standalone daemon mode, as opposed to being started with inetd. So, for example, if I have my configuration file with [global] pid file = /etc/rsync/rsyncd.pid

https://bugzilla.samba.org/show_bug.cgi?id=14260 Bug ID: 14260 Summary: leading / added to file name causing file not found when setting permissions Product: rsync Version: 3.1.3 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: core