Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    OS2    |    Fidonet International OS/2 Conference    |    3,371 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 2,889 of 3,371    |
|    Mike Powell to TORSTEN BAMBERG    |
|    Win 7 drive map problem    |
|    01 Jan 19 09:46:00    |
      > You know rsync?              No but after reading this I think I do need to know it. :)              > =##= Anfang "rsyndeam.cmd" =##=       > REM Dieses Script starten, und auf dem BSD-Rechner       > REM 192.168.0.19 (Unix) unter ~root/rsync       > REM das Script ./backup_mbox01 starten       > CD e:\dbahn\tool\rsync       > rsync.exe --daemon --config=rsync.conf --no-detach -v       > =##= Ende "rsyndeam.cmd" =##=       > This is the 'server' script on one of my OS/2 computers.       > Remotly rsync from one of the BSD Computers getting the files.       > You don't need smbfs or ndfs for this.              So, if I am reading this right, the rsyndeam.cmd runs on the OS/2 box,       allowing the BSD script ./backup_mbox01 to run on the BSD box. The BSD       script connects remotely to the OS/2 box.              My German translation of the comments is probably not great, so this       question may be answered, but I am thinking that the scripts run       independently and the OS/2 cmd script opens the channel for the connection       but does not cause the BSD script to run?              I assume the BSD script runs an rsync client?              This is great! :)              Mike              ---        * SLMR 2.1a * A restless eye across a weary room...        * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca