Thanks Jonathan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Marianu,
Jonathan
Sent: 27 October 2006 18:16
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] bpplsched columns
BPPLSCHED COLUMNS
Line 1
1 SCHED
2 SCHEDULE_NAME
3 TYPE (0
all
Does anyone have the
columns for the
bpplsched $policy
-l # output
What I'm trying to
do is get something together to overcome the bug where, calendar based
scheduling , we have a full monthly and full weekly running on the same day and
to avoid the weekly being selected as its
What I'm trying to do is get something together to overcome the bug
where, calendar based scheduling , we have a full monthly and full
weekly running on the same day and to avoid the weekly being selected as
its window is earlier.
=20
So I'm trying to at least give myself a heads up that a
: Friday, October 27, 2006
6:59 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] bpplsched
columns
all
Does anyone have the columns for the
bpplsched $policy -l # output
What I'm trying to do is get something
together to overcome the bug where
/attachment-0001.html
--
Message: 3
Date: Fri, 27 Oct 2006 14:58:32 +0100
From: Clooney, David [EMAIL PROTECTED]
Subject: [Veritas-bu] bpplsched columns
To: veritas-bu@mailman.eng.auburn.edu
Message-ID:
[EMAIL PROTECTED]
ca.com
Content-Type: text/plain
BPPLSCHED COLUMNS
Line 2
SCHEDWIN
SUNDAY START_TIME in seconds
...
Well that's the format of the line, but it's not guaranteed to be on
line 2. You'll have to parse the line identifier rather than counting.
Calendar scheduling will move it around.
Line 3 Residence for each copy
Line 4
