Re: glob exclude vs include behaviour

2018-01-24 Thread Kevin Korb via rsync
* isn't a shell glob in this case it is a simple pattern wildcard meaning "anything". On 01/24/2018 02:23 PM, Ken Chase via rsync wrote: > not a bug, buy colour me confused: > > /tmp/foo$ mkdir a > /tmp/foo$ touch a/foo > /tmp/foo$ touch a/.baz > /tmp/foo$ cd .. > /tmp$ rsync -avP --exclude=

glob exclude vs include behaviour

2018-01-24 Thread Ken Chase via rsync
not a bug, buy colour me confused: /tmp/foo$ mkdir a /tmp/foo$ touch a/foo /tmp/foo$ touch a/.baz /tmp/foo$ cd .. /tmp$ rsync -avP --exclude=a/* foo bar sending incremental file list created directory bar foo/ foo/a/ sent 71 bytes received 20 bytes 182.00 bytes/sec total size is 0 speedup

Re: What does this mean? select(1, [0], [], NULL, {60, 0}) = 0 (Timeout)

2018-01-24 Thread Paul Slootman via rsync
On Mon 22 Jan 2018, Kevin Korb via rsync wrote: > From man 2 select: > int select(int nfds, fd_set *readfds, fd_set *writefds, > fd_set *exceptfds, struct timeval *timeout); > > So, it is waiting for file descriptor #1 to become available with a 60 > second timeout which it is hitting. Actually:

RE: What does this mean? select(1, [0], [], NULL, {60, 0}) = 0 (Timeout)

2018-01-24 Thread Marc Roos via rsync
I take it that: - the file descriptors 1,2 here are either stdin or stdout (https://en.wikipedia.org/wiki/File_descriptor) - rsync client - server communication goes via stdin, stdout - servers are running ntpd Concluding from the new logs below. There is a problem on the client starting aroun