On Fri, Mar 1, 2013 at 10:34 AM, Michael Stowe
wrote:
>
>
>> On 01/03/13 09:42, upen wrote:
>>> On Thu, Feb 28, 2013 at 3:39 PM, Adam Goryachev
>>> wrote:
Quick reply, it needs the path to at on the windows machine, not the
Linux machine.
>>> wow, all this time I thought this was linux
> On 01/03/13 09:42, upen wrote:
>> On Thu, Feb 28, 2013 at 3:39 PM, Adam Goryachev
>> wrote:
>>> Quick reply, it needs the path to at on the windows machine, not the
>>> Linux machine.
>> wow, all this time I thought this was linux side. Thanks!!
>>
>> When I do which at on windows, I see , /cy
On 01/03/13 09:42, upen wrote:
> On Thu, Feb 28, 2013 at 3:39 PM, Adam Goryachev
> wrote:
>> Quick reply, it needs the path to at on the windows machine, not the Linux
>> machine.
> wow, all this time I thought this was linux side. Thanks!!
>
> When I do which at on windows, I see , /cygdrive/c/W
auth.sh needs to contain a valid user for the client machine (usually with
administrative privileges), as compared to the rsyncd user auths. It is
then used to remotely kick off scripts on the client side (as the user
specified in auth.sh).
Kris Lou
k...@themusiclink.net
On Thu, Feb 28, 2013 at
On Thu, Feb 28, 2013 at 3:39 PM, Adam Goryachev
wrote:
> Quick reply, it needs the path to at on the windows machine, not the Linux
> machine.
wow, all this time I thought this was linux side. Thanks!!
When I do which at on windows, I see , /cygdrive/c/WINDOWS/system32/at .
Is that correct path
The thing that I liked about this implementation (and had it bookmarked for
over a year before putting in place) is that it was relatively easy to
parse out with a minimum of shell scripting knowledge. As such, it is
easier to comprehend for somebody with a predominantly Windows background.
(Not
On Thu, Feb 28, 2013 at 9:53 AM, upen wrote:
> Hi,
>
> I have been trying to configure my winxp box to use the method from
> http://www.michaelstowe.com/backuppc/
>
> I emailed the blog owner but it's possible they are busy so haven't
> heard from them. Any help is appreciated.
>
> Here is the dum
On Thu, Feb 28, 2013 at 2:21 PM, Kris Lou wrote:
> auth.sh needs to contain a valid user for the client machine (usually with
> administrative privileges), as compared to the rsyncd user auths. It is
> then used to remotely kick off scripts on the client side (as the user
> specified in auth.sh).
> And this may be your real problem. Does your authentication work if
> you just back up the normal C$ share without the VSS stuff?
This is the think I should have had tried before (without VSS). I was
using cygwin/ssh/rsync method before, came to know from other
discussion that it doesn't use vs
Thanks.
On Thu, Feb 28, 2013 at 1:02 PM, Kris Lou wrote:
> How far have you traced the script execution chain? You should see winexe
> do call the appropriate scripts on the server side, and then a number of
> scripts also executing on the client side.
>
>>>/tmp/backuppc/preusercmd.sh: line 13:
How far have you traced the script execution chain? You should see winexe
do call the appropriate scripts on the server side, and then a number of
scripts also executing on the client side.
>>/tmp/backuppc/preusercmd.sh: line 13: at: command not found
Also, I specify the full path to "at" for th
On Thu, Feb 28, 2013 at 9:53 AM, upen wrote:
Not sure I can help much with specifics here, but I think those
'Unknown parameter' errors are harmless and from a samba4 based winexe
seeing your samba3 configs.
> CheckHostAlive: returning 0.353
> Executing DumpPreUserCmd: /tmp/backuppc/preusercmd.s
Hi,
I have been trying to configure my winxp box to use the method from
http://www.michaelstowe.com/backuppc/
I emailed the blog owner but it's possible they are busy so haven't
heard from them. Any help is appreciated.
Here is the dump tried from command prompt.
BackupPC_dump -v -f a.b.c.d
cmd
13 matches
Mail list logo
