SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 15 | April | 2004 ]

<< Previous Message << >> Next Message >>


Date: Thu, 15 Apr 2004 10:03:44 PDT7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: dSync (was: Hey Sheridan)

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Sheridan George wrote:
>
> I got this one. So, what did you do differently?

I sent it on the SCOUG-Help list. This message is also on the
SCOUG-Help list. Your ISP will accept mail from SCOUG, it just won't
accept mail from _me_.

> dSync was easy to set up. I got it working without any
> grief. It takes some time but I think I have a fix for
> that. I made several dSync.cfg files. I will, real soon
> now, make a REXX script that will copy a specific template
> to dSync.cfg, call dSync, and then copy a "NOP" template
> back to dsync.cfg.

The REXX script isn't necessary. Just use a separate .cmd for each of
the .cfg files, and specify the .cfg on the command line (that's what I
do).

For example, my dsync-MC.cmd file contains

dsync -v dsync-MC.cfg

which will run my dsync-MC.cfg script and show me what it's doing. The
-v option _does_ increase the execution time because it displays every
filename, so I minimize it as soon as I see that it's running okay.

> FWIW, I have templates to dSync
> 1) all of my main drive to my mirror drive,
> 2) the data partition to the mirror,
> 3) the applications partition to the mirror,
> 4) and a similar set to do the reverse.

I have the same on my system, so we think alike. Except I don't have
any .cfg files to "do the reverse" -- I don't want to accidentally run
the wrong script some day and remove all my new files.

> I claim success with dSync.

Good. Everybody seems to like it.

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 15 | April | 2004 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.