Re: Re.: Re: Problem with Client Option Sets
1998-12-14 12:07:53
Subject: |
Re: Re.: Re: Problem with Client Option Sets |
From: |
Bill Colwell <bcolwell AT DRAPER DOT COM> |
Date: |
Mon, 14 Dec 1998 12:07:53 -0500 |
In <412566DA.0052CF6C.00 AT smtpmta1.notes.intranet DOT pbs>, on 12/14/98
at 04:12 PM, Jan Soerensen <jan.g.soerensen AT PBS DOT DK> said:
>Chris
>When you try to define an INCLUDE statement via the "Client Option sets",
>it won't work. It is not supposed to.
>The only think regarding this subject, you can define in the "Client Option
>sets"
>is an INCLEXCL statement, which options is the name of a file, that
>contains INCLUDE and EXCLUDE statements. (Ex: INCLEXCL C:\XXX.OPT).
>You cannot define an INCLUDE or EXCLUDE statement via the "client option
>sets".
>Jan S rensen
>PBS Data A/S
>jgs AT pbs DOT dk
Defining includes and excludes in a client option set is supposed to work
and indeed, it does! Try running the following on your system --
/* */
/* macro file to define client options sets */
/* */
define cloptset ts1 desc='Test option sets'
commit
/* */
define clientopt ts1 changingretries 1 seq=10
define clientopt ts1 compressalways yes force=yes seq=20
define clientopt ts1 inclexcl "exclude /tmp/.../*"
define clientopt ts1 inclexcl "include ""*:\My Documents\...\*""" commit
Note the doubled quotes in the last define.
--
-----------------------------------------------------------
-----------------------------------------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
-----------------------------------------------------------
=========================================================================
|
|
|