Return-Path: 
 <user-return-1103-apmail-manifoldcf-user-archive=manifoldcf.apache.org@manifoldcf.apache.org>
X-Original-To: apmail-manifoldcf-user-archive@www.apache.org
Delivered-To: apmail-manifoldcf-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C7401D218
	for <apmail-manifoldcf-user-archive@www.apache.org>;
 Thu,  2 Aug 2012 17:13:25 +0000 (UTC)
Received: (qmail 65635 invoked by uid 500); 2 Aug 2012 17:13:25 -0000
Delivered-To: apmail-manifoldcf-user-archive@manifoldcf.apache.org
Received: (qmail 65607 invoked by uid 500); 2 Aug 2012 17:13:25 -0000
Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@manifoldcf.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@manifoldcf.apache.org>
List-Post: <mailto:user@manifoldcf.apache.org>
List-Id: <user.manifoldcf.apache.org>
Reply-To: user@manifoldcf.apache.org
Delivered-To: mailing list user@manifoldcf.apache.org
Received: (qmail 65599 invoked by uid 99); 2 Aug 2012 17:13:25 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Aug 2012 17:13:25 +0000
X-ASF-Spam-Status: No, hits=1.8 required=5.0
	tests=FREEMAIL_ENVFROM_END_DIGIT,FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of anupamb82@gmail.com
 designates 209.85.217.178 as permitted sender)
Received: from [209.85.217.178] (HELO mail-lb0-f178.google.com)
 (209.85.217.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Aug 2012 17:13:19 +0000
Received: by lbbgj10 with SMTP id gj10so1070842lbb.9
        for <user@manifoldcf.apache.org>;
 Thu, 02 Aug 2012 10:12:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=TB+hMx/blzKODNtchXfRzEJCQSUmff/MRHoULeE3NGM=;
        b=TmHArEFleHgEEjTn04J402s7d+dMK+HLbX1akoM7ZUiYkPpiOBRvyAgSLilYDTkVos
         28yal7qBvSDItfelVlylvo0jhH+hQglyUByY2W3t6gT6HXFvJIUBYQxtXQ62Cu6lSc/w
         luWs0Y6mFU8R+IS3K1T+hZl1HeG3LoKhAsv/YDeEY/hEgCC7rySKeRQegAiDng0wHr/3
         K8bu0JZOmZzijKVXYUBwdwpGT3nU4mtP/7bm9NH066EsQXSuEEYfEXY6JvX8OW6Z6Q7N
         KRDaw1NMhfeCc8a6XLBJj8vjsaV8rUQt8eotBfbIC+DSdMpTZLXeG+8xhV9fsFdozQnF
         EdIA==
MIME-Version: 1.0
Received: by 10.112.46.198 with SMTP id x6mr10196964lbm.19.1343927577798; Thu,
 02 Aug 2012 10:12:57 -0700 (PDT)
Received: by 10.114.13.234 with HTTP; Thu, 2 Aug 2012 10:12:57 -0700 (PDT)
Date: Thu, 2 Aug 2012 22:42:57 +0530
Message-ID: 
 <CAHOKQrx4qBfLEHy7dxX19pxgXWVMJ0jXG_3rwM52K6FyX7i=aQ@mail.gmail.com>
Subject: The Schedulars are not starting automatically
From: Anupam Bhattacharya <anupamb82@gmail.com>
To: user@manifoldcf.apache.org
Content-Type: multipart/alternative; boundary=bcaec5540604e0e87704c64b8527
X-Virus-Checked: Checked by ClamAV on apache.org

--bcaec5540604e0e87704c64b8527
Content-Type: text/plain; charset=ISO-8859-1

I have a Job which is indexing properly even the incremental indexing, if
initiated/Run manually. Although even after adding a specific time to Run
the schedular process the Jobs is not starting on its own.

What is the ideal configuration to configure a Job which run automatically
everyday at 12 am and does and incremental re-indexing (only look for those
document which are new OR modified after the last crawl) of the repository ?

Is it necessary to input/give the total run time details for adding a
specific schedule time.

Regards
Anupam

--bcaec5540604e0e87704c64b8527
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I have a Job which is indexing properly even the incremental indexing, if i=
nitiated/Run manually. Although even after adding a specific time to Run th=
e schedular process the Jobs is not starting on its own.<br><br>What is the=
 ideal configuration to configure a Job which run automatically everyday at=
 12 am and does and incremental re-indexing (only look for those document w=
hich are new OR modified after the last crawl) of the repository ?<br>
<br>Is it necessary to input/give the total run time details for adding a s=
pecific schedule time.<br clear=3D"all"><br>Regards<br>Anupam<br>

--bcaec5540604e0e87704c64b8527--