updater should run as a scheduled task and not as a service about omaha HOT 9 CLOSED

I think the "Run as User" portion of the scheduled tasks would be problematic 
for
something like this.

>Running an application all the time is just bad.

LOL. Seriously?

Ever heard of linux/unix daemons? 

This sounds more like a pet peave of sorin, than a defect.

Sir, I Agree.

Running the updates should be possible in two possible ways: background mode 
(no user
intervention) and manual mode.

Running in the background implies that no user intervention is required (ever): 
this
is something that is working very well with Task Scheduler.

Example from the linux *side* "yum -y update" : is something that does work 
very well
with crontab.

Background services, if done properly, have no measurable effect on the system. 

Google update is currently using 3MB of RAM on my system, 2MB of which is 
shared and 
most of the rest is swapped out.

As I understand it, if Task Scheduler is used it will require two 
implementations to 
support Win2K/XP (Task Scheduler 1.0, using ITaskScheduler) and Vista/7/2008 
(Task 
Scheduler 2.0, using ITaskService).

In addition, the Task Scheduler is itself a service, so I don't think you gain 
much 
by making use of it other than becoming tangled in the API and being beholden 
to 
whatever changes Microsoft decides to make for version 3.0.  Given that it's 
already 
working, I would vote to leave it as a stand-alone service.

I would however consider supporting a "shared" service (one that runs through 
svchost 
rather than as its own executable) since that would reduce the overhead even 
more.  I 
currently have one svchost instance hosting 17 separate system services and 
using 
only 8.5MB of private allocations.

Issue 4 has been merged into this issue.

Issue 6 has been merged into this issue.

As of version 1.2.183.7, Google Update uses the Task Scheduler instead of 
running all 
the time in most cases.

See http://google-opensource.blogspot.com/2009/07/google-update-regularly-
scheduled.html for the announcement and 
http://code.google.com/p/omaha/wiki/GoogleUpdateOnAScheduleOverview for an 
overview of 
the design.

I caught it running full-time again yesterday. I think the best option now is 
to just 
write a startup script that stops and deletes Google Update entirely whenever 
it 
manages to get reinstalled.