rsync Samba and Windoz
Scott Prive
Scott.Prive at storigen.com
Thu Sep 12 17:21:10 EDT 2002
One last option, if your daemon doesn't work on Windows:
you can use the Windows API to disable sleep mode, then restore the setting upon exit. I would be of no help in this area, but Cygwin does provide access to Win32 and it can be used with gcc.
> -----Original Message-----
> From: Jerry Feldman [mailto:gaf at blu.org]
> Sent: Thursday, September 12, 2002 4:08 PM
> To: discuss at blu.org
> Subject: Re: rsync Samba and Windoz
>
>
> No, for this purpose, I probably would set up a small Windows
> native daemon
> that would keep the system alive. I have not thought about
> exactly how I
> would implement it. SSHD is one of several methods.
>
> On 12 Sep 2002 at 15:10, ron.peterson at yellowbank.com wrote:
>
> > On Thu, Sep 12, 2002 at 02:44:20PM -0400, Scott Prive wrote:
> >
> > > With Cygwin on the box (I should read ahead before replying to a
> > > thread :-), you could just schedule a bash script on the *Windows*
> > > side, that pushes the data over.
> >
> > > Cygwin has a cron daemon you can enable, if for some
> reason the native
> > > NT scheduling thing (whatever it's called) does not do the trick.
> >
> > If using cron, you might like to put a passwordless public
> key in the
> > authorized_keys file on the sshd daemon side. Would you
> want to put a
> > public key generated on a Windows machine in your Linux box's
> > authorized_keys file? I'd do it the other way around.
> Alternatively,
> > use "command=" in the authorized_keys file to restrict the
> connection to
> > doing the backup operation. See 'man sshd' for the syntax.
> >
> > --
> > Ron Peterson -o)
> > 87 Taylor Street /\\
> > Granby, MA 01033 _\_v
> > https://www.yellowbank.com/ ----
>
>
> --
> Jerry Feldman <gaf at blu.org>
> Associate Director
> Boston Linux and Unix user group
> http://www.blu.org PGP key id:C5061EA9
> PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
>
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss
>
More information about the Discuss
mailing list