more problems reading the log...

This is a discussion on more problems reading the log... within the Rsync forums, part of the Networking and Network Related category; --===============0536632895== Content-Type: multipart/alternative; boundary="----=_Part_23894_7617620.1127766436313" ------=_Part_23894_7617620.1127766436313 Content-Type: text/plain; charset=ISO-8859-1 ...


Go Back   Usenet Forums > Networking and Network Related > Rsync

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 09-26-2005
Mario Tambos
 
Posts: n/a
Default more problems reading the log...

--===============0536632895==
Content-Type: multipart/alternative;
boundary="----=_Part_23894_7617620.1127766436313"

------=_Part_23894_7617620.1127766436313
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

i'd found something weird. this two lines are from a windows implementatio=
n
of rsync:
2005/09/22 20:05:33 [520] recv xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx] NMSCORE (=
)
BACKUP/IDS_HeartlandBank_db_200509220206.BAK 4449207808
2005/09/22 20:17:40 [520] rsync: write failed on
"/BACKUP/IDS_HeartlandBank_db_200509220831.BAK" (in NMSCORE): No space left
on device (28)
as you can see, the error below doesn't match the file name of the previou=
s
line.
i've read some logs from a novell implementation of rsync and it seems to
never happen that way. each error seems to point to the last file rsync
tried to send.
is that the way it works? that is a difference between the two
implementations of rsync?

------=_Part_23894_7617620.1127766436313
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<font size=3D"2">
<div>i'd found something weird. this two lines are from a windows implement=
ation of rsync:</div>
<div>&nbsp;</div>
<div>2005/09/22 20:05:33 [520] recv xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx] NMSCO=
RE () BACKUP/IDS_HeartlandBank_db_200509220206.BAK 4449207808</div>
<div>2005/09/22 20:17:40 [520] rsync: write failed on &quot;/BACKUP/IDS_Hea=
rtlandBank_db_200509220831.BAK&quot; (in NMSCORE): No space left on device =
(28)</div>
<div>&nbsp;</div>
<div>as you can see, the error below doesn't match the file name of the pre=
vious line.</div>
<div>&nbsp;</div>
<div>i've read some logs from a novell implementation of rsync and it seems=
to never&nbsp; happen that way. each error seems to point to the last file=
rsync tried to send.</div>
<div>&nbsp;</div>
<div>is that the way it works? that is a difference between the two&nbsp;im=
plementations of rsync?</div></font>

------=_Part_23894_7617620.1127766436313--

--===============0536632895==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
--===============0536632895==--
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 04:31 PM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0