Ok just after I read this email I turned on my monitor and saw an error
The instruction at "0x078a2b72" referenced at "0x077313cc". The memory could not be "written".
Click on OK to terminate the program
[OK]
Now what program did i just terminate? lol
A few of the memory heavy users are "WINLOGON.EXE" and "services.exe" and "LSASS.EXE"
_I_ have yet to really see why windows is so big in the server market, I know I probably need to know more before it works well but I find Linux WAY easier to use than windows server. With Linux what I have wanted to know was just a google away and ever since i started using Linux a year ago (looks at the date) and a few days ago I have never had any problems with it ( that i have not caused). With windows its been to much click here click there with no detail in what the click actually does (where as Linux in the config files they have what this and that does and sometimes why) and allot of the problems I google for windows I cant find the right help.
Travis R.
Shawn wrote:
My experience suggests that a Windows server will need to be rebooted about once a month to keep it stable. It is possible to minimize this if you check the running processes, and try restarting the service(s) that is/are eating up the resources. For instance, one of the servers I manage for a customer routinely uses more than 600Meg of RAM, running IIS, Cold Fusion, and SQL Server. When first started, it only needs approx 350 meg. Over a month the memory usage builds up, and I typically need to reboot, or at least stop the SQL services (it's claiming as much free space as possible). Part of that IS the application (multiple users can execute large queries simultaneously), but SQL Server doesn't do a great job of releasing the memory when it's through with it... Remedy? Reboot every month or so.... normally about the same time any security patches are installed - they usually force a reboot.
So, to sum it up, I think you're likely seeing routine stuff with Windows, but it might be worth digging a bit to see what's eating up the memory and processing time.... (Task Manager can give you a good hint...)
HTH.
Shawn
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
