| Subject: Re: CLI problems? |
| From: Stelv |
| Date: 23/06/2004, 21:11 |
I seem to remember someone saying a long time ago to make sure the hard
drives are not turned off after a while and not let the machine go into
hibernation. I just had the system turn off the monitor, but keep the
hard drives and everything running.
James J wrote:
holy_saiyan1@hotmail.com (Lamb Chop) expounded in
news:c5983d2.0406191610.28d243be@posting.google.com:
I've heard so much about the CLI and how fast it is compared to the
GUI, but I really haven't noticed the dramatic results that everyone
claims it has. I'm looking at a 1-2 hour reduction in WU time, from 45
hours to about 43 hours. I have it running with the -verbose option,
are there are any other -'s that i need to it run with in order to
speed it up? Also, I've tried almost all of the cachers out there,
and none of them seem to work. The only one that's worked for me was
SetiGate, and that was when I used the GUI. I might end up going back
to the GUI because I'm disappointed.
TIA/Keep searching!
You might try leaving off the -verbose option. It's been a while, but as
I recall, that gives you a steady stream of output. If so, it might be
slowing down the program. Try a WU or two without it and see if it makes a
difference. Beyond that, I don't know what to suggest. I don't know what
a normal processing time would be for that kind of system. 43 hours may be
the best you can do.
As for the cache programs, if you post some more specifics about the
problems you had, someone might be able to help. You should probably start
a separate thread for that.
James