Re: problem with rsync-daemon via ssh

2014-02-14 Thread Carlos Carvalho
Kevin Korb (k...@sanitarium.net) wrote on 13 February 2014 21:47: modules are defined in an rsyncd.conf file. That file needs to be in the home dir of the user. You mean the config file must be called rsyncd.conf instead of module? That'd be easy to solve but unfortunately it didn't work. I

Re: problem with rsync-daemon via ssh

2014-02-14 Thread Matthias Schniedermeyer
On 13.02.2014 23:38, Carlos Carvalho wrote: I'm trying to transfer something to another machine launching a once-only daemon through ssh with this command: rsync -avv -e ssh -l user ./orig/ machine::module/ where module is the name of a file in the home dir of user with the following:

Re: problem with rsync-daemon via ssh

2014-02-14 Thread Carlos Carvalho
Matthias Schniedermeyer (m...@citd.de) wrote on 14 February 2014 13:06: You mixed the options from remote shell with rsync daemon. Rsync is used either as 'rsync over SSH'(/remote shell) OR daemon-mode. No, there's a third method. Search for USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL

Re: problem with rsync-daemon via ssh

2014-02-14 Thread Paul Slootman
On Fri 14 Feb 2014, Matthias Schniedermeyer wrote: You mixed the options from remote shell with rsync daemon. Rsync is used either as 'rsync over SSH'(/remote shell) OR daemon-mode. Matthias, Ik recommend you check out the USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION part of the

Re: problem with rsync-daemon via ssh

2014-02-14 Thread Matthias Schniedermeyer
On 14.02.2014 13:17, Paul Slootman wrote: On Fri 14 Feb 2014, Matthias Schniedermeyer wrote: You mixed the options from remote shell with rsync daemon. Rsync is used either as 'rsync over SSH'(/remote shell) OR daemon-mode. Matthias, Ik recommend you check out the USING RSYNC-DAEMON

Re: problem with rsync-daemon via ssh

2014-02-14 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Try running that ssh command line yourself and see what it says. On 02/14/2014 06:34 AM, Carlos Carvalho wrote: Kevin Korb (k...@sanitarium.net) wrote on 13 February 2014 21:47: modules are defined in an rsyncd.conf file. That file needs to be in

[Bug 10448] New: Please include the --ignore-case patch by default

2014-02-14 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10448 Summary: Please include the --ignore-case patch by default Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5

[Bug 10449] New: Allow testing of supported parameter(s)

2014-02-14 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10449 Summary: Allow testing of supported parameter(s) Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5

SIGHUP signal

2014-02-14 Thread Grozdan
Hi, I'm new to the list so excuse me if this question has been asked before. Yesterday, I changed my rsyncd.conf file to add one more module to it. Then I sent a kill -HUP $pid signal to rsync running in daemon mode, but what gives? It just died so I had to start it up again. I though sending a

Re: /usr/bin/ssh not found when rsync is executed within rsnapshot

2014-02-14 Thread Chris Davies
On 10/02/14 05:38, Lorenz wrote: i have a problem. But let me first describe my setup. [...rsnapshot configuration...] cmd_ssh/usr/bin/ssh ssh_args-i /home/backupuser/.ssh/id_rsa rsync: Failed to exec /usr/bin/ssh -i /home/backupuser/.ssh/id_rsa: No such file or directory (2)

Re: SIGHUP signal

2014-02-14 Thread Hiroyuki Ikegami
Hi, I'm also new. Hello to all. Many softwares catches SIGHUP as a trigger to reload configurations. But it is a kind of software design. If the programmer does not want to write signal handling code, the programs received HUP just dies. So you should read a document to know what will be