Avast WEBforum
Business Products => Archive (Legacy) => Avast Business => Avast Distributed Network Manager => Topic started by: gprzybyl on May 19, 2004, 11:03:36 PM
-
I've noticed that the time in the events window is +4 hours from the system time. The time in the sessions window is +1 hour from the current system time. Otherwise so far so good.
-
Interesting. Does it have anything to do with the time zone set up on the systems??
-
I have one server client running for the purposes of the test in addition to the adnm machine. Both machines are in the Eastern Time Zone (GMT-5).
-
Something that might also be related or require a new thread is that I set up a discovery session with a Task Session expiration of 5 minutes. Two and a half hours later it is still running.
-
Something that might also be related or require a new thread is that I set up a discovery session with a Task Session expiration of 5 minutes. Two and a half hours later it is still running.
Well actually this is a bit confusing option. It doesn't really mean what you expected. The task expiration setting governs how much time the task job entry stays in the job queue, waiting to be picked up by a worker. It does not govern the time the task is let to run... (run time quota)
Consider client-side tasks: they work in such a way that whenever the task is run, a new entry is placed to each machine's job queue (each machine the task should be run on). Now, some of the machines pick up this entry almost immediately, but some don't (e.g. they're turned off as the user is on vacation). The expiration entry says after how much time the entry is automatically removed from the queue (marking the run on this machine as 'timed out')...
Hope this clears it a bit,
Vlk