Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
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
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |