From: bv@wjv.com (Bill Vermillion) Subject: Re: SCO Login Problems References: <NEBBLMPLNKHMEHJGNPIHEEAHFNAA.bill@mwdental.com>
<3f833b43.5890940@nntp> Date: Wed, 08 Oct 2003 02:55:02 GMT In article <3f833b43.5890940@nntp>, Peter McGill <pamcgill@rogers.com> wrote: >On Tue, 7 Oct 2003 20:07:43 GMT, Bill Andersen <bill@mwdental.com> >wrote: > >>Peter wrote: >>> Do you need 100% up time? >>> Are you running a web server or something else? >>> I am running a box which just requires login during office >>> hours. What I do is schedule it to reboot every night.
>>Peter, >>Not that this may not work as a temporary solution, but if it >>were me, I'd rather figure out WHY the login gets slow and fix >>THAT problem. I don't have an answer for "bernie" other than to >>keep looking for the problem. This "fix" will work in the short >>run, but even if you don't need 100% uptime, something isn't >>right on your box or the login wouldn't continue to get slower. >>And what other problems will get fixed when you figure out the >>cause of this one? Some you may not even know about... >>Peter, you haven't rubbed up against a Windows box lately have >>you? Wanting to reboot every night looks like a symptom of the >>Windows Viri <grin> > >True Fixing the cause of the problem is best. >My system doesn't have a specific problem that requires it to >reboot. >It's just been my experience, that every computer and every >operating system, wether unix, windows, or whatever needs to be >rebooted every once in a while. Even unix gets dead processes >stuck in memory that there is no other way to get rid of. >Programs have memory leaks, etc... If you don't have a regular >reboot schedule then eventually the problems stack up and cause >noticable side effects, even bringing down the whole server. >True unix is better at managing these problems than other >operating systems, but it is not immune.
I've never noticed that on the servers I run - they just keep running and running. I do make it a point to do a complete OS upgrade every two years however and that requires a reboot. Around the first of the year I rebuilt the entire OS on the webserver and it's been up for 245 days now - while before I restarted it [actually moved to a new machine that was indentical except for a much larger hard drive] it was at about 780 days. It just never falters, hicups or slows down. It peaks in the spring running about 80-90K hits/day. Comes up on the top of the Google sites because of a stong domain name, so that helps the traffic. The mail machine has shown a bit of slowness in bursts lately but that because of the huge amount of spam coming in - and during those peaks it's getting about 10/second - and rejecting about 75% of them :-) A machine I remotely maintain in D.C. just was rebooted two week ago after running for 750+days. They lost power during the big storm and it is not in a colo. I've stopped having clients reboot their SCO systems since the lbolt problem was fixed. I did notice a flaw in the time on an OSR 5.0.5 - in that about after 14 months the uptime in w/who went away. Totally blank. In the past 5+ years the OSes have become very stable from my POV. Maybe you have hardware problems. I've never had one of these machine just stop working. Fairly plain machines - the servers are running iNTEL mobos with some Tyans - the OSR5 are most often ASUS. >Since our severs don't need to be up all day, I just get ahead >of the problem and reboot frequently. Simple but effective. Well mine need to be up all the time but never need to be rebooted. The one exception was a dedicated server that unexplicably lost one of the NIC ports on the mobo. So that one required a hands on visit and a reboot. Bill -- Bill Vermillion - bv @ wjv . com
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar