| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Win 7 drive map problem |
> 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) SEEN-BY: 15/0 18/200 19/36 20/4609 34/999 90/1 104/57 116/18 120/331 123/140 SEEN-BY: 153/7715 218/700 220/60 222/2 230/150 152 240/1120 250/1 261/38 100 SEEN-BY: 261/1466 266/404 512 267/155 275/100 282/1031 1056 291/1 111 320/119 SEEN-BY: 320/219 340/400 342/13 396/45 633/267 280 640/1384 712/132 620 848 SEEN-BY: 770/1 801/161 189 2320/105 3634/12 5020/1042 @PATH: 2320/105 261/38 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.