Improve your productivity and save time.  Let your system work for you.
HiTek Software Home
Subject Fundamentals of the Directory Change task
Date   08/15/2006
Message Hi Melvin,

thank you for your answer.

Sorry, but I have some more questions:

How I can stop a "directory change" task ? Or is it possible to see the running of the task - maybe in the task manager ... Because if I start this task as daemon (max. waiting time 1440 minutes), I can't see if this task is still running. I have tried to stop the task with stopping the schedule engine, but the task was still running. So I had to restart the server.

When I use the "directory monitor" then I have to schedule this task, so that a certain directory or subdirectory is under control. If I schedule this task every 1 minute, then it's the same if a make a "directory change" task with polling every 60 sec (max. waiting time 1440 minutes) without using as daemon ? Is it right, if I use the daemon, then a havent't schedule this task ? But If I do not use the daemon with a max. waiting time 1440 minutes and start this task, then the task launchs the whole day for changes in the directory ? So why I have to use the daemon ? And is the polling time important just without using daemon ?

You see I'm a little confused. I hope you can help me. Do you know a forum in the internet with experience from other people using Automize ?


Reply1 Thanks for using Automize. 

1) The task runs within the engine, so if you shut down the engine the task will stop. You must have set the Scheduler Menu / Scheduler settings option to be "wait for tasks to finish before shutting down engine" . Thats why the task still ran, because previous instance of engine waited for it. See the Help file in the Scheduler Settings dialog for details on this option.

2) For the Directory Change, it is not recommended to run it manually. The task is not really a daemon, but acts like one if you schedule the task daily (every 1 day) and set the max wait time = 1440. The polling time should be set to 1 minute. When one schedule ends the other begins and this way the task runs continously like a daemon. For example, with above settings: One task schedule will run for 1 day. It will poll the directory every 1 minute. If change is found, it will trigger other desired task and keep polling, thus daemon effect. This task schedule will be done in 1440 minutes and quit. Since the Scheduling Period is 1 day (1440) minutes, the next schedule will kick in at same time, thus giving the daemon effect.

3) It is very IMPORTANT to match the maximum wait time and the schedule Period to prevent overlapping for tasks. Also there is no way to stop a running task, so be very careful when starting/scheduling a Directory Change task.

3) Scheduling the task to run every one minute (and running for 1 minute) is not efficient since the scheduler has to launch 1440 tasks to have the same effect as scheduling every 1 day.

4) There is no forum, but we have an Knowledge Base available via our support page. All useful email support technical discussions are added there. This discussion between us will be added to the email database.

-- Sincerely, Melvin Desilva Hitek Software