I think the inclexcl one is right but you need to include a number to
specify which order to process the options...
-----Original Message-----
From: Walker, Lesley R [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 09, 2000 1:16 AM
To: [EMAIL PROTECTED]
Subject: Re: Option file and optionset
Ron Pavan wrote:
> example in my env:
> all server side option sets for "excludes" are set with override = no
> all server side option sets for "includes" are set with override = yes
>
[etc]
While we're on this topic, can someone give an example of the syntax (3.7.3
on Solaris) to specify an include/exclude statement in the client option
set? I've read the Admin Ref, and tried a couple of ways but it comes back
with errors:
DEF CLIENTO FRED EXCLUDE /foo/*
results in: Invalid option name - EXCLUDE"
DEF CLIENTO FRED INCLEXCL "/path/filename"
DEF CLIENTO FRED INCLEXCL "ex /foo/*"
both result in: DEFINE CLIENTOPT: Invalid option value
(and yes, the file exists in the first one)
What am I doing wrong?
Why doesn't the manual have an example, dammit?
Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.
