Guido Schmidt wrote:
> Matthias Meyer schrieb:
>   
>> Guido Schmidt wrote:
>>
>>     
>>> Matthias Meyer wrote:
>>>       
>>>> Guido Schmidt wrote:
>>>>         
>>>>> What works? The opening and closing of the tunnel.
>>>>> What does not? The connection to it. Nothing in the rsyncd-logs on
>>>>> host.example.com.
>>>>>
>>>>> If I leave DumpPostUserCmd empty the tunnel stays open and I can use it
>>>>> with rsync as user backuppc on a shell providing the password by hand:
>>>>>
>>>>>   rsync -av --list-only --port=32323 backuppc@localhost::Alles
>>>>>   /home/backuppc/test/
>>>>>
>>>>>           
>>>> Do you provide the password during your script?
>>>>         
>>> The ssh-connection works (authenticated via public key). The password I
>>> refered to is for connecting to rsyncd and that is stored in
>>> $Conf{RsyncdPasswd}.
>>>
>>> It seems that backuppc does not reach the point where it actually tries
>>> to connect to rsync daemon. There are no entries in the rsyncd-log
>>> (there are when I use the rsync-command above). How can I find out more
>>> what happens and what not?
>>>
>>>       
>> I don't really know what the problem :-(
>> You can increase the loglevel with $Conf{XferLogLevel}.
>>     
>
> I already increased it to 6, but that didn't give any more details.
>
>   
>> What happens if you start your tunnel interactive and leave DumpPreUser as 
>> well
>> as CmdDumpPostUserCmd empty.
>>     
>
> Okay, we're getting closer. That way the backup worked.
> So I either get BackupPC to open the tunnel or to do the backup. That's odd.
>   

I'd try giving an explicit exit value upon successful tunnel creation.

...
--- /usr/local/bin/sshtunnelcontrol.orig        2009-12-22 
03:16:34.000000000 -0900
+++ /usr/local/bin/sshtunnelcontrol     2009-12-22 03:17:09.000000000 -0900
@@ -27,6 +27,9 @@
       if ! ps -ef|grep -E "^backuppc $PID" ; then
         echo "$PRG_NAME: Error: Tunnel does not exist"
         exit 1
+      else
+        echo "$PRG_NAME: Info: Tunnel exists"
+        exit 0
       fi
     else
       echo "$PRG_NAME: Error: ${PIDFILE} already exists."
...

>   
>> Why do you need the identification by rsync? I would believe you can trust 
>> your
>> ssh-tunnel and dont't need an additional authentication.
>>     
>
> There a users with shell-access to that host. Not protecting the port
> would give them read-access to the whole file-system.
>
> Guido
>   

Chris


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/