Just wanted to follow up, it seems my problem is with winexe and kerberos...
If I get it working I will send the solution. Thanks
Rod
On 9/23/07 9:34 AM, "Rod Dickerson" <[EMAIL PROTECTED]> wrote:
> Yeah sorry, I thought about that after I sent the message. I should have
> included the scripts. I am setting the path in the script, so I think it
> should work. From watching ps¹ during execution, it seems to be having
> problems with this particular line, although I have commented it out and it
> does get further, but still hangs on something else:
>
> cltinstalled=`$wincmd //$1 "cmd.exe /c if exist c:\rsyncd\rsync.exe (echo 1)
> else echo 0"|sed -e "s/$err//g"|tr [:cntrl:] :|sed 's/://g'`
>
> But when I run it from su - -s /bin/bash backuppc¹ (my daemon user), it runs
> fine.
>
> Basically what I am doing is:
>
> 1. calling dev-pre-backup-vista.sh using DumPreUsrCmd.
> 2. it checks to see if the ³client² (rsync) is installed, and if not then it
> copies the files. During the install it sets a unique password for the machine
> and puts that in ryncd.secrets and /etc/BackupPC/pc/host.pl.
> 3. The script uses winexe, which is a remote command executor for Windows that
> runs on Linux. I take the output from several commands and put those into
> variables which I use in the script to determine what to do. It uses kerberos
> authentication to communicate with the client.
> 4. It mounts the latest vista snapshot as X:, then starts rsyncd exporting X:.
> 5. It checks to make sure that it really started rsyncd, and that it is
> listening (it takes a bit). It loops a timer a few times to make sure it is
> running.
> 6. It exits.
>
> I have something similar for XP, but it is a bit trickier since I have to
> create the snapshot and mount it. I have the same issues though, it seems to
> run fine from su backuppc, but not from the daemon. Thanks for any help...
>
> Rod
>
>
> On 9/22/07 6:24 AM, "Matthias Meyer" <[EMAIL PROTECTED]> wrote:
>
>> Am Freitag 21 September 2007 21:48 schrieb Rod Dickerson:
>>> > I have a pre-script that works great when I su to the backuppc user, but
>>> > when I run it from the daemon it just hangs. Should there be any
>>> > difference in how the scripts are processed with these 2 methods? I can¹t
>>> > really tell that it is doing anything wrong in the logs, but it just
>>> > doesn¹t complete. Are there any syntax issues or other problems that I
>>> > need to be aware of? Thanks
>> It is heavy to analyze a unknown script ;-)
>> I know problems with PATH under linux which can be the reason. This
>> environment variable can be different initialized between user and daemon
>> modes.
>> Maybee you can insert a "echo $PATH" in your script.
>> br
>> Matthias
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
