Re: How to set absolute path for rsync?

2017-08-30 Thread Paul Slootman via rsync
On Tue 15 Aug 2017, Joe Qiao via rsync wrote:

> Thanks so much for the quick reply, Kevin!
> 
> I tried with ssh and --partial-dir, it looks the partial file still will be
> stored in local dir, but not in /tmp.
> 
> 
> Every 1.0s: ls -al /home/joe/rsync/ /tmp/
> Tue Aug 15 17:29:30 2017
> 
> /home/joe/rsync/:
> total 408840
> drwxr-xr-x  2 root root  4096 Aug 15 17:29 .
> drwxr-xr-x 32 joe  joe   4096 Aug 15 15:01 ..
> *-rw---  1 root root 418643968 Aug 15 17:29 .flash_image.14WoMV

No, you misunderstand the meaning of "partial" here.

--partial-dir is where the partially transferred file is stored if rsync
is interrupted with --partial (I'm not sure if --partial-dir implies
--partial, it probably does).

It does NOT mean where the temporary files are stored during transfer.


Paul

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: Clarifications on getting debug information when rsync freezes

2017-08-30 Thread Paul Slootman via rsync
On Wed 16 Aug 2017, Vangelis Katsikaros via rsync wrote:
> 
> I am having a problem with rsync freezing and I would like to collect the 
> proper information while the problem happens. However, I would like to ask 
> some clarifications.
> 
> rsync-debug
> ===
> 
> I see references of using rsync-debug but I cannot figure out how to use it 
> *while* the rsync is stuck. If I understand from various replies in this 
> email list it must be given as an argument to rsync beforehand?
> 
> If I do not want to change something in my current rsync setup, would it be 
> ok to do sth like this on the destination machine:
> 
> # 1. find the ssh PID from the source IP
> destination_machine $ sudo netstat -atlp | grep "192.168.23"
> tcp0 36 192.168.40.23:ssh   192.168.23.40:49187 
> ESTABLISHED 915/sshd: abc [priv
> 
> # 2. find all related processes
> destination_machine $ sudo pstree --show-pids 915
> sshd(915)───sshd(1079)───rsync(1082)───rsync(1085)
> 
> # 3. then strace these all these

Well, you'll miss anything leading up to the hang, but doing it this may
show something significant, but perhaps not.


Paul

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: rsync got stuck

2017-08-30 Thread Paul Slootman via rsync
On Wed 23 Aug 2017, Vangelis Katsikaros via rsync wrote:

> abc   3797  3796  0 01:12 ?00:03:14 /usr/bin/rsync --compress 
> --compress-level=9 --bwlimit=512k --recursive --delay-updates --quiet 
> --update --exclude=/.* /SRC_PATH/ DEST_IP:/DEST_PATH/

Try running rsync without the --compress option, that has been the
source of problems in the past.
If you do need compression you could add that at the ssh level.


Paul

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

an integer overflow issue in rsync-3.1.2

2017-08-30 Thread shqking via rsync
Hello all,

I reported an integer overflow issue in the bugzilla (
https://bugzilla.samba.org/show_bug.cgi?id=12568), but I haven't received
any response so far.

I was wondering could you please take a look at this report and give me
some feedback.

Thanks and look forward to your reply.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Two log files instead of one?

2017-08-30 Thread Michal Ruprich via rsync
Hi all,

I'm a bit confused about the log-file option for the daemon rsync.

What the rsyncd.conf manual page says about the 'log file' option in
rsyncd.conf:

"This setting can be overridden by using the --log-file=FILE or
--dparam=logfile=FILE command-line options.  The former overrides all
the log-file parameters of  the  daemon  and all  module  settings."

And the rsync manual page in the daemon section says:

"This option tells the rsync daemon to use the given log-file name
instead  of  using  the "log file" setting in the config file."

From this I would assume that when I run the daemon like this:
$/usr/bin/rsync --daemon --log-file=/tmp/rsync_test.log --no-detach
"$OPTIONS", I would get one log file - /tmp/rsync_test.log. Instead when
I run rsync from a remote client, two log files are created. There is a
piece of information in the /var/log/rsyncd.log file (the default one
from /etc/rsyncd.conf) and another piece of information in
rsync_test.log. Is this how it is supposed to work or is it a bug?

Thanks.

Michal Ruprich


-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html