On Sun, Apr 02, 2006 at 09:45:27AM +0200, Julian Pace Ross wrote:
> It seems not, and I must say that the bad behaviour as described by Matt's
> reply the other day, persisted even after solely applying the
> clientserver.c patch you had posted.
I don't see any such problem after that patch. You
Since my original problem was that logging goes to syslog when use ssh and per-user conf files, I figured this was needed.
So I *can* have non-daemon logging on the server side, when using ssh, without this patch?
It seems not, and I must say that the bad behaviour as described by Matt's reply the
On Sat, Apr 01, 2006 at 12:40:45PM +0200, Julian Pace Ross wrote:
> I downloaded 2.6.7, carefully applied the log-file.diff patch, then
> applied the patch Wayne posted yesterday.
Why did you apply the log-file.diff patch? That is for non-daemon
logging, and it has not had much testing. I just l
OK I can confirm the following daemon behavior, maybe this will give further clues...
All the following is without ssh, just straight to the daemon on port 873.
case 1) running the daemon with 2.6.7: log file specified in rsyncd.conf as /var/log/rsyncd.log
Result: everything works fine and messag
Some bad news unfortunately.. what I did is exactly this:
I downloaded 2.6.7, carefully applied the log-file.diff patch, then applied the patch Wayne posted yesterday.
What's happenning now is that nothing is being logged in either the syslog or the specified log file in the per-user conf file.
I
OK! ... will recompile and fire-up.
Thanks Wayne
On 31/03/06, Wayne Davison <[EMAIL PROTECTED]> wrote:
On Fri, Mar 31, 2006 at 06:11:38PM +0200, Julian Pace Ross wrote:> What is bothering me is that I lost the ability to write in any file
> other than syslog (/var/log/messages)The problem turned
On Fri, Mar 31, 2006 at 06:11:38PM +0200, Julian Pace Ross wrote:
> What is bothering me is that I lost the ability to write in any file
> other than syslog (/var/log/messages)
The problem turned out to be that a new "connect ..." message was
getting output in the wrong spot. The attached patch f
Yep guys thats exactly it!
I'm running 2.6.7pre3.
Just tried the syslog facility option and it didnt work either.
I'll keep trying to get out some clues before delving into the src...
Let me know if you find anything.
Cheers
Julian
On 31/03/06, Matt McCutchen <[EMAIL PROTECTED]> wrote:
On Fri, 2
On Fri, 2006-03-31 at 18:50 +0200, Julian Pace Ross wrote:
> Yep I tried those two options, and nothing...
> Even if the pre-user conf files have a log file in the same directory,
> which I touch before trying, messages keep going to syslog... I tried
> with 666 permissions on rsyncd.log too just
On Fri, Mar 31, 2006 at 08:56:26AM -0800, Wayne Davison wrote:
> A single-use daemon can write its own logfile; it just needs write-
> permissions on the file
Sorry, I just noticed that 2.6.7 has a bug in this area, so I'm looking
into a fix. (Should have done a confirmation test before speaking.
Yep I tried those two options, and nothing...
Even if the pre-user conf files have a log file in the same directory, which I touch before trying, messages keep going to syslog... I tried with 666 permissions on rsyncd.log too just to make sure...
The following is one of the user's conf file,
At 11:36 5-8-2003 -0700, you wrote:
> Today I received the error again:
>
> Received disconnect from IP: 2: fork failed: Resource temporarily
> unavailable
>
> rsync: connection unexpectedly closed (0 bytes read so far)
> rsync error: error in rsync protocol data stream (cod
On Tue, Aug 05, 2003 at 01:19:43PM +0200, René van der Kroft wrote:
> At 01:04 30-7-2003 -0700, you wrote:
>
> >> The follwing error showed up today in the logfile:
> >>
> >> Received disconnect from IP: 2: fork failed: Resource temporarily
> >> unavailable^M
> >> rsync: connection unexpectedly cl
On Fri, Aug 08, 2003 at 12:27:00PM +0200, René van der Kroft wrote:
> At 11:36 5-8-2003 -0700, you wrote:
> >> Today I received the error again:
> >>
> >> Received disconnect from IP: 2: fork failed: Resource temporarily
> >> unavailable
> >>
> >> rsync: connection unexpectedly clos
At 01:04 30-7-2003 -0700, you wrote:
> The follwing error showed up today in the logfile:
>
> Received disconnect from IP: 2: fork failed: Resource temporarily
> unavailable^M
> rsync: connection unexpectedly closed (0 bytes read so far)
> rsync error: error in rsync protocol data stream (code 12)
On Thu, Jul 31, 2003 at 09:29:25AM +0200, René van der Kroft wrote:
> At 01:04 30-7-2003 -0700, you wrote:
> >> Today the rsync run again, the backup directory shows that there where no
> >> file changed.
> >> The Internet statistics for that connection shows: IN 14M, OUT
> >> 133M! (Incoming on I
At 01:04 30-7-2003 -0700, you wrote:
> Today the rsync run again, the backup directory shows that there where no
> file changed.
> The Internet statistics for that connection shows: IN 14M, OUT
> 133M! (Incoming on IP port 22, outgoing keep state)
> That while the logs shows that there where no fi
On Wed, Jul 30, 2003 at 09:45:53AM +0200, René van der Kroft wrote:
> At 02:42 29-7-2003 -0700, you wrote:
> >On Tue, Jul 29, 2003 at 10:55:56AM +0200, René van der Kroft wrote:
> >>
> >> All the files are transferred successfully but logging doesn't work OK.
> >> When I add a file into the /home d
At 02:42 29-7-2003 -0700, you wrote:
On Tue, Jul 29, 2003 at 10:55:56AM +0200, René van der Kroft wrote:
>
> All the files are transferred successfully but logging doesn't work OK.
> When I add a file into the /home directory rsync picks him up and
transfers
> him to the server, but when I look in
On Tue, Jul 29, 2003 at 10:55:56AM +0200, René van der Kroft wrote:
>
>
> Hi,
>
> I'm using rsync version 2.5.5 on OpenBSD 3.3 to backup the users /home
> directory over the Internet. It's started by a cron job every night. For
> logging I've add the -vv parameter and redirect the output to a
Hi,
I'm using rsync version 2.5.5 on OpenBSD 3.3 to backup the users /home
directory over the Internet. It's started by a cron job every night. For
logging I've add the -vv parameter and redirect the output to a logfile.
Like this:
rsync -vv --stats --archive --delete --backup --backup-dir=/
21 matches
Mail list logo
