search for: logfname

...core dumps are never good :-( Here'a a proposed patch to fallback to syslog if opening the log file fails: --- ../cvstree/rsync/log.c 2003-03-25 03:28:54.000000000 +0100 +++ ./log.c 2003-11-17 13:31:15.000000000 +0100 @@ -134,9 +134,9 @@ static void logit(int priority, char *buf) { - if (logfname) { - if (!logfile) - log_open(); + if (logfname && !logfile) + log_open(); + if (logfile) { fprintf(logfile,"%s [%d] %s", timestring(time(NULL)), (int)getpid(), buf); fflush(logfile); @@ -164,9 +164,11 @@ if (logfname) { if (*logfname) {...

...ot; }, { RERR_CMD_FAILED , "remote shell failed" }, { RERR_CMD_KILLED , "remote shell killed" }, { RERR_CMD_RUN, "remote command could not be run" }, *************** *** 89,96 **** static void logit(int priority, char *buf) { if (logfname) { ! if (!logfile) log_open(); fprintf(logfile,"%s [%d] %s", timestring(time(NULL)), (int)getpid(), buf); fflush(logfile); --- 90,103 ---- static void logit(int priority, char *buf) {...

Hi, I get strange time entries in the rsync log, For example: 2006/07/02 14:56:12 [20054] rsync to upload/aspen/nhm from plxc6266.pdx.intel.com (10.25.26.90) 2006/07/02 11:56:22 [20054] wrote 28 bytes read 3582404 bytes total size 32030720 The first entry in the correct time and second is strange. I checked and this is not the time on the destination. Any ideas what is the

...177,7 @@ /* * allocate a new file list */ -struct file_list *flist_new() +struct file_list *flist_new(void) { struct file_list *flist; --- log.c.orig Mon Dec 23 21:51:47 2002 +++ log.c Mon Dec 23 21:51:54 2002 @@ -183,7 +183,7 @@ #endif } -void log_open() +void log_open(void) { if (logfname && !logfile) { extern int orig_umask; @@ -193,7 +193,7 @@ } } -void log_close() +void log_close(void) { if (logfile) { fclose(logfile); --- popt/popt.c.orig Mon Dec 23 21:51:59 2002 +++ popt/popt.c Mon Dec 23 21:59:21 2002 @@ -443,9 +443,10 @@ } /* Make a copy we...

...TRING(lp_socket_options, &Globals.socket_options) FN_GLOBAL_INTEGER(lp_syslog_facility, &Globals.syslog_facility) diff -Nuar rsync-2.5.6/log.c rsync-2.5.6.new/log.c --- rsync-2.5.6/log.c Mon Dec 23 23:42:04 2002 +++ rsync-2.5.6.new/log.c Sat Apr 12 23:57:54 2003 @@ -137,11 +137,17 @@ if (logfname) { if (!logfile) log_open(); - fprintf(logfile,"%s [%d] %s", - timestring(time(NULL)), (int)getpid(), buf); + if (lp_log_timestamp()) { + fprintf(logfile,"%s ", timestring(time(NULL))); + } + if (lp_log_pid()) { + fprintf(logfile,"[%d] ", (int)getpid(...

Hi guys: First post for me on this list. THE PROBLEM =========== I have several linux servers (ranging from Redhat 7.3 to FC3) that use Rsync (version 2.6.8 and 2.6.7, read on for reasons) to backup their data. A typical rsync backup script looks like this: ------------------------------------------------------------------------------------------ #!/bin/sh RSYNC_PASSWORD=<PASSWORD> rsync