Re: unable to open configuration file rsyncd.conf

This is a discussion on Re: unable to open configuration file rsyncd.conf within the Rsync forums, part of the Networking and Network Related category; This is a multipart message in MIME format. --===============0371625733== Content-Type: multipart/alternative; boundary="=_alternative 000AC4798625706A_=" This is ...


Go Back   Usenet Forums > Networking and Network Related > Rsync

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 08-27-2005
Tim.Clashin@calcucare.com
 
Posts: n/a
Default Re: unable to open configuration file rsyncd.conf

This is a multipart message in MIME format.
--===============0371625733==
Content-Type: multipart/alternative;
boundary="=_alternative 000AC4798625706A_="

This is a multipart message in MIME format.
--=_alternative 000AC4798625706A_=
Content-Type: text/plain; charset="US-ASCII"

Thanks Paul for the info on regarding where rsyncd.conf should be when ssh
logins. I moved rsyncd.conf to the user home directory, and it looked
like the transfer was going to start but then I got Segmentation Fault
core dumps. So I just used root as the login and the transfer worked like
a champ.

Appreciate the help and I will also look at 2.6.6. Thanks everyone.

Tim Clashin



Paul Slootman <paul@debian.org>
Sent by: rsync-bounces+tclashin=calcucare.com@lists.samba.org
08/26/2005 03:55 AM

To
rsync@lists.samba.org
cc

Subject
Re: unable to open configuration file rsyncd.conf






On Thu 25 Aug 2005, Tim.Clashin@calcucare.com wrote:

> Today from the client I want to just copy over to the server what files
> have changed today.
>
> So my command from the client is the following:
>
> /usr/local/bin/rsync --partial --progress --stats -az -e "ssh -p 22"
> /"directory on the client" USER@boxA::modulename
>
> I do get a connection to Box B but after I enter the user's password

thru
> ssh, I get the following the client:


[...]

> this is what is produced on the server /var/adm/messages:
> rsyncd[19422]: [ID 702911 daemon.warning] rsync: rsync: unable to open
> configuration file "rsyncd.conf": No such file or directory (2)
> rsyncd[19422]: [ID 702911 daemon.warning] rsync error: syntax or usage
> error (code 1) at clientserver.c(512)
> rsyncd[19436]: [ID 702911 daemon.warning] rsync: rsync: unable to open
> configuration file "rsyncd.conf": No such file or directory (2)
> rsyncd[19436]: [ID 702911 daemon.warning] rsync error: syntax or usage
> error (code 1) at clientserver.c(512)
>
> On the server I am running rsync in daemon mode by using this command,
>
> /usr/local/bin/rsync --deamon --config /etc/rsyncd.conf, and the daemon

is
> running, but the client is still get the unable to find

/etc/rsyncd.conf.

If you supply -e ssh ... as parameters to rsync in combination with the
:: syntax, ssh is used to start a new rsync in daemon mode. If you're
not doing that as root, the default location for the config file is
rsyncd.conf in the current directory (typically $HOME). Hence it can't
find rsyncd.conf in ~USER/.

This isn't stated that clearly in the manpage, this might be mentioned
in the CONNECTING TO AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM
section... the distinction between that section and the RUNNING AN RSYNC
SERVER OVER A REMOTE SHELL PROGRAM section is a bit vague as well.


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


--=_alternative 000AC4798625706A_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Thanks Paul for the info on regarding
where rsyncd.conf should be when ssh logins. &nbsp;I moved rsyncd.conf
to the user home directory, and it looked like the transfer was going to
start but then I got Segmentation Fault core dumps. &nbsp;So I just used
root as the login and the transfer worked like a champ. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Appreciate the help and I will also
look at 2.6.6. &nbsp;Thanks everyone. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Tim Clashin</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Paul Slootman &lt;paul@debian.org&gt;</b>
</font>
<br><font size=1 face="sans-serif">Sent by: rsync-bounces+tclashin=calcucare.com@lists.samba.org</font>
<p><font size=1 face="sans-serif">08/26/2005 03:55 AM</font>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">rsync@lists.samba.org</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">Re: unable to open configuration
file rsyncd.conf</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>On Thu 25 Aug 2005, Tim.Clashin@calcucare.com wrote:<br>
<br>
&gt; Today from the client I want to just copy over to the server what
files <br>
&gt; have changed today. <br>
&gt; <br>
&gt; So my command from the client is the following:<br>
&gt; <br>
&gt; /usr/local/bin/rsync --partial --progress --stats -az -e &quot;ssh
-p 22&quot; <br>
&gt; /&quot;directory on the client&quot; USER@boxA::modulename<br>
&gt; <br>
&gt; I do get a connection to Box B but after I enter the user's password
thru <br>
&gt; ssh, I get the following the client:<br>
<br>
[...]<br>
<br>
&gt; this is what is produced on the server /var/adm/messages:<br>
&gt; rsyncd[19422]: [ID 702911 daemon.warning] rsync: rsync: unable to
open <br>
&gt; configuration file &quot;rsyncd.conf&quot;: No such file or directory
(2)<br>
&gt; rsyncd[19422]: [ID 702911 daemon.warning] rsync error: syntax or usage
<br>
&gt; error (code 1) at clientserver.c(512)<br>
&gt; rsyncd[19436]: [ID 702911 daemon.warning] rsync: rsync: unable to
open <br>
&gt; configuration file &quot;rsyncd.conf&quot;: No such file or directory
(2)<br>
&gt; rsyncd[19436]: [ID 702911 daemon.warning] rsync error: syntax or usage
<br>
&gt; error (code 1) at clientserver.c(512)<br>
&gt; <br>
&gt; On the server I am running rsync in daemon mode by using this command,<br>
&gt; <br>
&gt; /usr/local/bin/rsync --deamon --config /etc/rsyncd.conf, and the daemon
is <br>
&gt; running, but the client is still get the unable to find /etc/rsyncd.conf.
<br>
<br>
If you supply -e ssh ... as parameters to rsync in combination with the<br>
:: syntax, ssh is used to start a new rsync in daemon mode. If you're<br>
not doing that as root, the default location for the config file is<br>
rsyncd.conf in the current directory (typically $HOME). Hence it can't<br>
find rsyncd.conf in ~USER/.<br>
<br>
This isn't stated that clearly in the manpage, this might be mentioned<br>
in the CONNECTING TO AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM<br>
section... the distinction between that section and the RUNNING AN RSYNC<br>
SERVER OVER A REMOTE SHELL PROGRAM section is a bit vague as well.<br>
<br>
<br>
Paul Slootman<br>
-- <br>
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync<br>
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html<br>
</font></tt>
<br>
--=_alternative 000AC4798625706A_=--

--===============0371625733==
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
--===============0371625733==--
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 11:02 AM.


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